NEWS & UPDATES >> BCA BCSP064 Synopsis & Project Work Started for DEC 2017, IGNOU MCA MCSP060 Synopsis Work Started for DEC 2017, CONTACT 4 IGNOU Mini Project
Showing posts with label VIVA Question Answer. Show all posts
Showing posts with label VIVA Question Answer. Show all posts

IGNOU VIVA SELECTED QUESTION ANSWER

VIVA PREPARATION FOR IGNOU BCA MCA STUDENTS 
Dear BCA MCA Aspirants,
Greetings from IGNOUFriend Team,
We are very happy to inform you that you can prepare viva and clear viva exam to following as per mention sample question answer.

It is divided in two types
FIRTS - Formal Question for BCA MCA Students
SECOND - Technical Question for BCA MCA Students (Technical Question from PHP, MYSQL, CSS, HTML, HTML-5,JavaScript, .Net with C#, Sql Server, Java, Ms-Access etc as per your project category.)

NiPS Institute (NiPSAR) successfully serve many students to crack IGNOU Exam, Synopsis, Project, Viva, other career, other university related query and many more. We found that after association of NiPS and tecINDIA we able to provide you best Learning as well as Live working platform for your successful career.
Our focus is to support you to clear your paper and help to reach your destination, And We know your first goal is getting degree from University. So, do smart learning get support and achieve your success. You are born to be successful and you have to do it J
Now focus on study as well as viva and get solution from project report, Internet, Books etc. ->

Step1: Be formal, Dress formal at viva time
Step2: Get overview of project report and keep CD with source code
Step3: Think…you are able to crack viva because you revise your project report.
Step4: Don't bother if you are not able to understand coding part.
Step5: Get prepared with below nontechnical and technical question.

All the best

Happy Learning!! Wish you success J
FORMAL QUESTION FOR BCA MCA STUDENTS : CRACK YOUR VIVA EXAM Easily  - Click Here : PART II

TECHNICAL QUESTION & ANSWER for VIVA Prepration
PHP | My SQL | 








ASP.NET with C# |






SQL SERVER |


IGNOU BCA MCA Students - VIVA Question Answer for SQL Server Part II


JAVA | JSP | APPLET | 

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part I

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part II

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part III

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part IV

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part V

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part VI

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part VII

IGNOU BCA MCA Students - VIVA Question Answer for JAVA APPLET Part VIII

IGNOU BCA MCA Students - VIVA Question Answer for JAVA APPLET Part IX

IGNOU BCA MCA Students - VIVA Question Answer for JAVA or JSP Part X

IGNOU BCA MCA Students - VIVA Question Answer for JAVA Servlet Part XI

IGNOU BCA MCA - VIVA Question Answer for JAVA - JSP Part XII

IGNOU BCA MCA - PROJECT VIVA Question Answer for JAVA - JSP Part XIII


IGNOU BCA MCA - PROJECT VIVA Question Answer for JAVA - JSP Part XIV


TESTING Selected Question Answer

IGNOU BCA MCA Testing Viva Question Answer Part I


Powered by IGNOUFriend | www.ignou-project.com |
ignou bca mca synopsis, ignou class, ignou bca mca project, solved ignou assignment,BCA Coaching Institute in Delhi, MCA Coaching Institute in Delhi, BCA MCA Coaching Institute in Delhi, BCA MCA, Tuation Class in delhi, IGNOU BCA MCA Class, IGNOU BCA MCA Tution,IGNOU Solved Assignment, IGNOU BCA Synopsis , IGNOU MCA Synopsis, ignou bca project, ignou mca project, ignou best coaching in delhi, ignou best coaching in new delhi, ignou best coaching in south delhi, ignou best coaching in north delhi, ignou best coaching in east delhi, ignou best coaching in west delhi
ignou, bca, mca, coaching institute, tution class, bcsp064, mcsp060, cs76, mcs044,bcs011, bcs012, mcs011, mcs012, mcs013, mcs015, bcsl021, bcsl022, mcs014, bcs040, mcs021, mcs023, bcs031, bcsl032, bcsl033, bcsl 034, bcs041, bcs042, mcsl016, bcsl043, bcsl044, bcsl045, bcs051, bcs052, bcs053, bcs054, bcs055, bcsl056, bcsl057, bcsl058, bcs062, mcs022, bcsl063, project
mcsp060, mcse011, mcse004, mcse003, mcsl054, mcs053, mcs052, mcs051, mcsl045, mcs044, mcs043, mcs042, mcs041, mcsl036, mcs035, mcs034, mcs033, mcs032, mcs031, mcsl025, mcs024, mcs023, mcs022, mcs021, mcsl017, mcsl016, mcs015, mcs014, mcs013, mcs012, mcs011
nips institute, nipsar, ignoufriend.in, ignou-project.com, ignouhelp, best coaching institute
Posted by

IGNOU VIVA IMPORTANT QUESTION ANSWER

IMPORTANT QUESTION ANSWER for IGNOU BCA MCA Students & Other Computer Science Students


HTML



PHP - MySQL Question Answer

SDLC - Question Answer from Software Engineering

Powered by IGNOUFriend | www.ignou-project.com |
ignou bca mca synopsis, ignou class, ignou bca mca project, solved ignou assignment,BCA Coaching Institute in Delhi, MCA Coaching Institute in Delhi, BCA MCA Coaching Institute in Delhi, BCA MCA, Tuation Class in delhi, IGNOU BCA MCA Class, IGNOU BCA MCA Tution,IGNOU Solved Assignment, IGNOU BCA Synopsis , IGNOU MCA Synopsis, ignou bca project, ignou mca project, ignou best coaching in delhi, ignou best coaching in new delhi, ignou best coaching in south delhi, ignou best coaching in north delhi, ignou best coaching in east delhi, ignou best coaching in west delhi
ignou, bca, mca, coaching institute, tution class, bcsp064, mcsp060, cs76, mcs044,bcs011, bcs012, mcs011, mcs012, mcs013, mcs015, bcsl021, bcsl022, mcs014, bcs040, mcs021, mcs023, bcs031, bcsl032, bcsl033, bcsl 034, bcs041, bcs042, mcsl016, bcsl043, bcsl044, bcsl045, bcs051, bcs052, bcs053, bcs054, bcs055, bcsl056, bcsl057, bcsl058, bcs062, mcs022, bcsl063, project
mcsp060, mcse011, mcse004, mcse003, mcsl054, mcs053, mcs052, mcs051, mcsl045, mcs044, mcs043, mcs042, mcs041, mcsl036, mcs035, mcs034, mcs033, mcs032, mcs031, mcsl025, mcs024, mcs023, mcs022, mcs021, mcsl017, mcsl016, mcs015, mcs014, mcs013, mcs012, mcs011
nips institute, nipsar, ignoufriend.in, ignou-project.com, ignouhelp, best coaching institute
Posted by

What is USE Case Diagram & FAQ

USE CASE Diagram and its related important Question Answer

Here we have some frequently asked questions (FAQ) about or related to use case diagrams. If you have some question not in the list or can provide a better answer, you can suggest those at the bottom of the page as a comment.

What are requirements?
Requirements describe external view of a system, system's externally observable characteristics (phenotype). Older approach to requirements is to describe what a system should do without specifying how it does it.

How requirements are collected?
There are different methods of requirements elicitation. To collect requirements:
·         recognize the problem being experienced, or
·         determine the opportunities to better serve customers,
·         ascertain external system behavior that could address those problems or opportunities,
·         document the list of the problems, opportunities, and desired behaviors as requirements.

What are different types of requirements?
Some types of requirements are:
·         Functional requirements - what the system should do.
·         Quality (or non-functional) requirements - how fast, reliable, secure system should be.
·         Data requirements - what data should be stored by system.

What are functional requirements?
Functional requirements describe what the system should do in terms of system's input, system's behavior in response to that input, and output back to the user of the system. Generally, functional requirements are expressed in the form "The system shall <do><requirement>", for example, "The system shall accept guest check-in request and allocate a room."

Are use cases the same as functional requirements or functional requirements are different from use cases?
Functional requirements could be collected and documented using different approaches, techniques, tools, and templates. Use cases were created by Ivar Jacobson in 1986 to support visual modeling of functional requirements. Use cases became one of the most widely used approaches for capturing functional requirements for object-oriented systems as part of UML and Rational Unified Process (RUP). It is now a common practice to express functional requirements as use cases, described in both graphical and narrative form.

What is use case diagram?
Use case diagram is UML diagram which shows some business or software system, its external users (called actors), and a set of actions (called use cases) that users of the system should or can perform while using the system. Use case diagrams are used to describe functionality of a system from the point of view of external users.

What is use case?
Each use case describes a unit of complete and useful functionality that business or system provides to its users, how external user interacts with a system to achieve a desired result. Some examples of use cases: Hire employee, Buy ticket, Place order, Deposit funds.

What is actor in use case diagrams?
Actor represents some group (called "role") of external customers or users of the business or software system. Actors have some needs and require specific services from the system. Some examples of actors are: Customer, Student, and Passenger. Actor could be not just human but also another system, business, or device.

What is the difference between use case diagram and use case?
Use case diagram shows business or system, its external users, and use cases applicable to the system. Use case represents one specific goal or need of the user from the system


Posted by No comments:

What is Software Design and its Level

What is Software Design and its Level Complete Question Answer.
Software design is a process to transform user requirements into some suitable form, which helps the programmer in software coding and implementation.
For assessing user requirements, an SRS (Software Requirement Specification) document is created whereas for coding and implementation, there is a need of more specific and detailed requirements in software terms. The output of this process can directly be used into implementation in programming languages.
Software design is the first step in SDLC (Software Design Life Cycle), which moves the concentration from problem domain to solution domain. It tries to specify how to fulfill the requirements mentioned in SRS.

Software Design Levels

Software design yields three levels of results:
  • Architectural Design - The architectural design is the highest abstract version of the system. It identifies the software as a system with many components interacting with each other. At this level, the designers get the idea of proposed solution domain.
  • High-level Design- The high-level design breaks the 'single entity-multiple component' concept of architectural design into less-abstracted view of sub-systems and modules and depicts their interaction with each other. High-level design focuses on how the system along with all of its components can be implemented in forms of modules. It recognizes modular structure of each sub-system and their relation and interaction among each other.
  • Detailed Design- Detailed design deals with the implementation part of what is seen as a system and its sub-systems in the previous two designs. It is more detailed towards modules and their implementations. It defines logical structure of each module and their interfaces to communicate with other modules.

What is Modularization

Modularization is a technique to divide a software system into multiple discrete and independent modules, which are expected to be capable of carrying out task(s) independently. These modules may work as basic constructs for the entire software. Designers tend to design modules such that they can be executed and/or compiled separately and independently.
Modular design unintentionally follows the rules of 'divide and conquer' problem-solving strategy this is because there are many other benefits attached with the modular design of a software.
Advantage of modularization:
  • Smaller components are easier to maintain
  • Program can be divided based on functional aspects
  • Desired level of abstraction can be brought in the program
  • Components with high cohesion can be re-used again
  • Concurrent execution can be made possible
  • Desired from security aspect

What is Concurrency

Back in time, all software are meant to be executed sequentially. By sequential execution we mean that the coded instruction will be executed one after another implying only one portion of program being activated at any given time. Say, a software has multiple modules, then only one of all the modules can be found active at any time of execution.
In software design, concurrency is implemented by splitting the software into multiple independent units of execution, like modules and executing them in parallel. In other words, concurrency provides capability to the software to execute more than one part of code in parallel to each other.
It is necessary for the programmers and designers to recognize those modules, which can be made parallel execution.

Example

The spell check feature in word processor is a module of software, which runs along side the word processor itself.


Posted by No comments:

What is Cohesion and Coupling

What is Cohesion and Coupling important Question Answer in Details


When a software program is modularized, its tasks are divided into several modules based on some characteristics. As we know, modules are set of instructions put together in order to achieve some tasks. They are though, considered as single entity but may refer to each other to work together. There are measures by which the quality of a design of modules and their interaction among them can be measured. These measures are called coupling and cohesion.

Cohesion

Cohesion is a measure that defines the degree of intra-dependability within elements of a module. The greater the cohesion, the better is the program design.
There are seven types of cohesion, namely –
  • Co-incidental cohesion - It is unplanned and random cohesion, which might be the result of breaking the program into smaller modules for the sake of modularization. Because it is unplanned, it may serve confusion to the programmers and is generally not-accepted.
  • Logical cohesion - When logically categorized elements are put together into a module, it is called logical cohesion.
  • Temporal Cohesion - When elements of module are organized such that they are processed at a similar point in time, it is called temporal cohesion.
  • Procedural cohesion - When elements of module are grouped together, which are executed sequentially in order to perform a task, it is called procedural cohesion.
  • Communicational cohesion - When elements of module are grouped together, which are executed sequentially and work on same data (information), it is called communicational cohesion.
  • Sequential cohesion - When elements of module are grouped because the output of one element serves as input to another and so on, it is called sequential cohesion.
  • Functional cohesion - It is considered to be the highest degree of cohesion, and it is highly expected. Elements of module in functional cohesion are grouped because they all contribute to a single well-defined function. It can also be reused.

Coupling

Coupling is a measure that defines the level of inter-dependability among modules of a program. It tells at what level the modules interfere and interact with each other. The lower the coupling, the better the program.
There are five levels of coupling, namely -
  • Content coupling - When a module can directly access or modify or refer to the content of another module, it is called content level coupling.
  • Common coupling- When multiple modules have read and write access to some global data, it is called common or global coupling.
  • Control coupling- Two modules are called control-coupled if one of them decides the function of the other module or changes its flow of execution.
  • Stamp coupling- When multiple modules share common data structure and work on different part of it, it is called stamp coupling.
  • Data coupling- Data coupling is when two modules interact with each other by means of passing data (as parameter). If a module passes data structure as parameter, then the receiving module should use all its components.
Ideally, no coupling is considered to be the best.

What is Design Verification

The output of software design process is design documentation, pseudo codes, detailed logic diagrams, process diagrams, and detailed description of all functional or non-functional requirements.
The next phase, which is the implementation of software, depends on all outputs mentioned above.
It is then becomes necessary to verify the output before proceeding to the next phase. The early any mistake is detected, the better it is or it might not be detected until testing of the product. If the outputs of design phase are in formal notation form, then their associated tools for verification should be used otherwise a thorough design review can be used for verification and validation.
By structured verification approach, reviewers can detect defects that might be caused by overlooking some conditions. A good design review is important for good software design, accuracy and quality.
What is User Interface

User interface is the front-end application view to which user interacts in order to use the software. User can manipulate and control the software as well as hardware by means of user interface. Today, user interface is found at almost every place where digital technology exists, right from computers, mobile phones, cars, music players, airplanes, ships etc.
User interface is part of software and is designed such a way that it is expected to provide the user insight of the software. UI provides fundamental platform for human-computer interaction.
UI can be graphical, text-based, audio-video based, depending upon the underlying hardware and software combination. UI can be hardware or software or a combination of both.
The software becomes more popular if its user interface is:
  • Attractive
  • Simple to use
  • Responsive in short time
  • Clear to understand
  • Consistent on all interfacing screens
UI is broadly divided into two categories:
  • Command Line Interface
  • Graphical User Interface

Command Line Interface (CLI)

CLI has been a great tool of interaction with computers until the video display monitors came into existence. CLI is first choice of many technical users and programmers. CLI is minimum interface a software can provide to its users.
CLI provides a command prompt, the place where the user types the command and feeds to the system. The user needs to remember the syntax of command and its use. Earlier CLI were not programmed to handle the user errors effectively.
A command is a text-based reference to set of instructions, which are expected to be executed by the system. There are methods like macros, scripts that make it easy for the user to operate.
CLI uses less amount of computer resource as compared to GUI.

CLI Elements

A text-based command line interface can have the following elements:
·        Command Prompt - It is text-based notifier that is mostly shows the context in which the user is working. It is generated by the software system.
·        Cursor - It is a small horizontal line or a vertical bar of the height of line, to represent position of character while typing. Cursor is mostly found in blinking state. It moves as the user writes or deletes something.
·        Command - A command is an executable instruction. It may have one or more parameters. Output on command execution is shown inline on the screen. When output is produced, command prompt is displayed on the next line.
Posted by No comments:

What is Graphical User Interface GUI

What is Graphical User Interface GUI Detail Answer

Graphical User Interface provides the user graphical means to interact with the system. GUI can be combination of both hardware and software. Using GUI, user interprets the software.
Typically, GUI is more resource consuming than that of CLI. With advancing technology, the programmers and designers create complex GUI designs that work with more efficiency, accuracy and speed.

GUI Elements

GUI provides a set of components to interact with software or hardware.
Every graphical component provides a way to work with the system. A GUI system has following elements such as:
·        Window - An area where contents of application are displayed. Contents in a window can be displayed in the form of icons or lists, if the window represents file structure. It is easier for a user to navigate in the file system in an exploring window. Windows can be minimized, resized or maximized to the size of screen. They can be moved anywhere on the screen. A window may contain another window of the same application, called child window.
·        Tabs - If an application allows executing multiple instances of itself, they appear on the screen as separate windows. Tabbed Document Interface has come up to open multiple documents in the same window. This interface also helps in viewing preference panel in application. All modern web-browsers use this feature.
·        Menu - Menu is an array of standard commands, grouped together and placed at a visible place (usually top) inside the application window. The menu can be programmed to appear or hide on mouse clicks.
·        Icon - An icon is small picture representing an associated application. When these icons are clicked or double clicked, the application window is opened. Icon displays application and programs installed on a system in the form of small pictures.
·        Cursor - Interacting devices such as mouse, touch pad, digital pen are represented in GUI as cursors. On screen cursor follows the instructions from hardware in almost real-time. Cursors are also named pointers in GUI systems. They are used to select menus, windows and other application features.

Application specific GUI components

A GUI of an application contains one or more of the listed GUI elements:
·        Application Window - Most application windows uses the constructs supplied by operating systems but many use their own customer created windows to contain the contents of application.
·        Dialogue Box - It is a child window that contains message for the user and request for some action to be taken. For Example: Application generate a dialogue to get confirmation from user to delete a file.
·        Text-Box - Provides an area for user to type and enter text-based data.
·        Buttons - They imitate real life buttons and are used to submit inputs to the software.
·        Radio-button - Displays available options for selection. Only one can be selected among all offered.
·        Check-box - Functions similar to list-box. When an option is selected, the box is marked as checked. Multiple options represented by check boxes can be selected.
·        List-box - Provides list of available items for selection. More than one item can be selected.
Other impressive GUI components are:
  • Sliders
  • Combo-box
  • Data-grid
  • Drop-down list

User Interface Design Activities

There are a number of activities performed for designing user interface. The process of GUI design and implementation is alike SDLC. Any model can be used for GUI implementation among Waterfall, Iterative or Spiral Model.
A model used for GUI design and development should fulfill these GUI specific steps.
·        GUI Requirement Gathering - The designers may like to have list of all functional and non-functional requirements of GUI. This can be taken from user and their existing software solution.
·        User Analysis - The designer studies who is going to use the software GUI. The target audience matters as the design details change according to the knowledge and competency level of the user. If user is technical savvy, advanced and complex GUI can be incorporated. For a novice user, more information is included on how-to of software.
·        Task Analysis - Designers have to analyze what task is to be done by the software solution. Here in GUI, it does not matter how it will be done. Tasks can be represented in hierarchical manner taking one major task and dividing it further into smaller sub-tasks. Tasks provide goals for GUI presentation. Flow of information among sub-tasks determines the flow of GUI contents in the software.
·        GUI Design & implementation - Designers after having information about requirements, tasks and user environment, design the GUI and implements into code and embed the GUI with working or dummy software in the background. It is then self-tested by the developers.
·        Testing - GUI testing can be done in various ways. Organization can have in-house inspection, direct involvement of users and release of beta version are few of them. Testing may include usability, compatibility, user acceptance etc.
Posted by No comments: