SOFTWARE ENGINEERING UNIT II PART A

1. List the project deliverables shown during the project development. Documents Demonstration of functions Demonstration of subsystems Demonstration of accuracy Demonstration of reliability, security or performance. 2. Why we use Critical Path Method? Minimum amount of time taken to complete a project is called critical path method. We use CPM, in order to estimate each activity's derivation and reveal those activities that are most critical to completing the project on time. 3. What is meant by Slack time and how it is calculated? Slack time for an activity is the difference between the availability time and the real time for the activity. Slack time = available time real time. 4. What is meant by egoless approach? Egoless approach is the one which holds everyone in the team are same. Moreover the process is separated from the individuals; criticism is made of the product or the result, not the people involved. The egoless team structure is democratic and all the team members vote on decision whether it concerns design considerations or testing techniques. 5. How the risk exposure be calculated? The risk exposure can be calculated using the formula, Risk Exposure = Risk impact * Risk probability 6. Outline the steps involved in Risk management. Steps involved in risk management are, 1. Risk Assessment 1. Risk identification 2. Risk Analysis 3. Risk Prioritization 2. Risk Control 1.Risk reduction 2. Risk Mgmt. planning 3. Risk resolution 7. What are the two statistics used in assessing the accuracy? The two statistics used in assessing the accuracy are, 1. PRED(x/100) is the percentage of projects for which the estimate is within x% of the actual value. 2. MMRE is the mean magnitude of relative error, so we hope that the MMRE for a particular model is very small.
SEC/IIICSE/SE

8. List the items involved in a good project plan. 1. Project scope 2. Project schedule 3. Project team organization 4. Technical description of the proposed system 5. Project standards, procedures, and proposed techniques and tools 6. Quality assurance plan 7. Configuration management plan 8. Documentation plan 9. Data management plan 10. Resource management plan 11. Test plan 12. Training plan 13. Security plan 14. Risk management plan 15. Maintenance plan 9. What is a functional requirement and nonfunctional or quality requirement? Functional requirement: It describes required behavior in terms of required activities such as relations to inputs and the state of each entity before and after an activity occurs. Quality requirement or Nonfunctional Requirement: It describes some quality characteristics that the software solution must posses such as fast response time, easy of use, high reliability or low maintenance cost. 10. Difference between process and design constraint? Design constraint 1. It is a design decision. 2. It is the platform or interface components that has already been made and that restricts the set of solutions to our problem. Process constraint

1. It is a restriction on the techniques or resources. 2. It can be used to build the system.

11. Define requirement definition and requirement specification? Requirement definition: It is aimed at a business audience such as clients, customers and users. Requirement specification: It is aimed at a technical audience such as designers, testers and project manager. 12. Define the terms: class-scope attribute, class-scope operations, association, aggregate association, composition. Class-scope attributes: It is represented as an underlined attribute, is a data value hat is shared by all instances of the class. Class-scope operation: It is an underlined operation, is an operation performed by the abstract class rather than by the instance classes. Association:

SEC/IIICSE/SE

A line between two classes, called an association, indicates a relationship between the classes entities. Aggregate association: It is drawn as an association with a white diamond at one end, where the class at the diamond end is the aggregate. Composition: It is the special type of aggregation in which instances of the compound class are physically constructed from instances of the component class. 13. Compare evolutionary and throwaway prototyping Throwaway prototyping 1. It is software that is developed to learn more about a problem or about a proposed solution. 2. Eg:Quick-and-dirty software. Evolutionary prototyping 1. It is developed not only to help to answer questions but also to be incorporated into the final product. 2.Eg:response rate, modularity

14. What is requirement elicitation? Requirement elicitation is an especially critical part of the process. We must use a variety of techniques to determine what the users really want. It is the process of collecting users requirement. 15. What is software cost reduction (SCR)? Software cost reduction (SCR) is a collection of techniques that were designed to encourage software developers to employ good software-engineering design principles. 16. Define: Requirement Engineering Requirement engineering is the systematic use of proven principles, techniques, language and tools for the cost effective analysis, documentation, and on-going evolution of user needs and the specification of the external behavior of a system to satisfy those needs. (Or) What is requirement engineering? Requirement engineering is the process of establishing the services that the customer requires from the system and the constraints under which it operates and is developed. 17. What are the various types of traceability in software engineering? a. Source traceability These are basically the links from requirement to stakeholders who propose these requirements. b. Requirements traceability These are links between dependant requirements. c. Design traceability These are links from requirements to design. 18. Define software prototyping. Software prototyping is defined as a rapid software development for validating the requirements.

19. What are the benefits of prototyping?

SEC/IIICSE/SE

a. b. c. d. e.

Prototype serves as a basis for deriving system specification. Design quality can be improved. System can be maintained easily. Development efforts may get reduced. System usability can be improved.

20. What are the prototyping approaches in software process? a. Evolutionary prototyping In this approach of system development, the initial prototype is prepared and it is then refined through number of stages to final stage. Problems Management problems Maintenance problem Verification

b. Throw-away prototyping Using this approach a rough practical implementation of the system is produced. The requirement problems can be identified from this implementation. It is then discarded. System is then developed using some different engineering paradigm. Problems It can be undocumented. Changes made during the software development proceed may degrade the system structure. Sometimes organizational quality standard may not be strictly applied.
(Or) Compare Evolutionary prototyping and Throw away prototyping Evolutionary prototyping The principle objective of Evolutionary prototyping model is to deliver the working system to the end-user. The process of development starts with well understood requirements. It must be developed for the systems where the specification cannot be developed in advance. Throw away prototyping The principle objective of Throw away prototyping model is to validate or derive the system requirements. The process of development starts with poorly understood requirements. The Throw away prototype is developed to reduce the requirements risks

21. What are the advantages of evolutionary prototyping? a. Fast delivery of the working system. b. User is involved while developing the system. c. More useful system can be delivered. d. Specification, design and implementation work in co-coordinated manner. 22. What are the various Rapid prototyping techniques? a. Dynamic high level language development. b. Database programming. c. Component and application assembly. 23. What is the use of User Interface prototyping? This prototyping is used to pre-specify the look and feel of user interface in an effective way.
SEC/IIICSE/SE

24. What are the characteristics of SRS? a. Correct The SRS should be made up to date when appropriate requirements are identified. b. Unambiguous When the requirements are correctly understood then only it is possible to write unambiguous software. c. Complete To make SRS complete, it should be specified what a software designer wants to create software. d. Consistent It should be consistent with reference to the functionalities identified. e. Specific The requirements should be mentioned specifically. f. Traceable What is the need for mentioned requirement? This should be correctly identified. 25. What are the objectives of Analysis modeling? a. To describe what the customer requires. b. To establish a basis for the creation of software design. c. To devise a set of valid requirements after which the software can be built. 26. Compare functional and behavioral modeling Behavioral modeling The Behavioral modeling represents how system behaves. The Behavioral model is represented by state chart diagrams. The Behavioral model gives the abstract repre

Functional modeling The Functional model depicts all the essential functionalities of the system. The Functional model is represented by data flow and control flow diagrams. The Functional diagram gives detailed scenario of system which has to be developed.

27. What is data modeling? Data modeling is the basic step in the analysis modeling. In data modeling the data objects are examined independently of processing. The data model represents how data are related with one another. 28. What is a data object? Data object is a collection of attributes that act as an aspect, characteristic, quality, or descriptor of the object. 29. What is ERD? Entity Relationship Diagram is the graphical representation of the object relationship pair. It is mainly used in database applications. 30. What is DFD? Data Flow Diagram is a graphical representation that depicts the information flow and the transforms that are applied on the data as it moves from input to output. The basic form of a DFD, also known as a data flow graph or a bubble chart. 31. What does Level0 DFD represent? Level0 DFD is called as fundamental system model or context model. In the context model the entire software system is represented by a single bubble with input and output indicated by incoming and outgoing arrows.
SEC/IIICSE/SE

32. What is a state transition diagram? State transition diagram is basically a collection of states and events. The events cause the system to change its state. It also represents what actions are to be taken on the occurrence of particular event. 33. State the four generic activities of requirement engineering? Requirement engineering involves four generic activities such as: 1. Feasibility study 2. Requirements Elicitation and Analysis 3. Requirements specification and documentation 4. Requirements validation 34. What are the purposes of building software prototypes? 1. To develop a system for user interface. 2. To develop a system to validate requirements. 3. To demonstrate application feasibility. 4. To avoid risk on assumption based building and 5. More clear study on application.

35. What are the different steps that described the requirement engineering process?
The different steps that described the requirement engineering process are,

Requirements Elicitation Requirements analysis and negotiation Requirements specification

System modeling Requirements validation Requirements management

36. What is Requirements Elicitation?

Requirements Elicitation involves asking the customer, the users, and other what the objective for the system or product are, what is to be accomplished, how the system or product fits into the needs of the business, and finally, how the system or product is to be used on a day-to-day basis.

37. Why Requirements Elicitation process is difficult?

The following are the reasons, i. Problems of scope ii. Problems of understanding iii. Problems of volatility 38. What types of models do we create during requirement analysis? Functional model Data model Behavioral model 39. What is usage of models? To understand the system
SEC/IIICSE/SE

 Serves as a focal point of review Foundation for design 40. What does functional model stands for? Functional model shows the series of transformation that are made on data or information on moving through software. It describes how the system functions to produce the required output for the set of input supplied to it. Functional model involves Data Flow Diagrams. 41. What does Behavioral model stands for? A model that depicts softwares reaction to some external events is known as behavioral modeling. The State Transition Diagram (STD) represents the behavior of a system by depicting its states and events that cause the system to change state. 42. What guidelines should we follow while analyzing the requirements? Understand before creating a analysis model. Develop a prototype to understand the system. Record the reasons for every requirement Rank the requirements Eliminate ambiguity

43. What is meant by feasibility study?

A feasibility study is a short focused study which reports the recommendation whether or not it is worth carrying system development process. Feasibility study that checks, Whether the system contributes to the organizational objectives. If the system can be engineered using current technology and within budget. 44. What are the different types of requirements? User requirements System requirements Interface requirements 45. What are the various kinds of requirement documents? User requirements definition document System requirements specification document 46. List the classification of software system requirements. (Or) What are the board categories of system requirements? Software system requirements are often classified as follows Functional Requirements Non- Functional Requirements Domain Requirements

47. What are Functional Requirements? (Or) Define: Functional Requirements.

Functional Requirements are statements of services the system should provide how the system should react to particular input and how the system should behave in particular situation.
SEC/IIICSE/SE

Functional Requirements: Describe functionality or system services. Depend on the type of software, expected users and the type of the system where the software is used.

48. What are Non-Functional Requirements? (Or) Define: Non-Functional Requirements. Non-Functional Requirements are constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc Non-Functional Requirements: Define system properties and constraints eg: reliability, response time and storage requirements Non-Functional Requirements may be more critical than Functional Requirements. 49. Classify Non-Functional Requirements. Non-Functional Requirements can be classified based on how they are derived as: Product Requirements Organizational Requirements External Requirements 50. What are user requirements? Users Requirements should describe Functional and NonFunctional requirements so that they are understandable by system users who dont have detailed technical knowledge. Users Requirements are defined using natural language, tables and diagrams. 51. What are system requirements? System requirements are, More detailed specification of user requirements. Serve as a basis for designing the system. May be used as part of the system contract. 52. List the advantages of Evolutionary prototyping Advantages Fast delivery of the working system. User is involved while developing the system. More useful system can be delivered. Specification, design and implementation work is co-ordinated manner. 53. Define Stakeholder. Stakeholder: Anyone who has stake in successful outcome of Project Business Managers, end-users, software engineer, support people 54. How the Process Model differ from one another? Based on flow of activities Interdependencies between activities Manner of Quality Assurance
SEC/IIICSE/SE

Manner of Project Tracking Team Organization and Roles Work Products identify an requirement identifier

55. What is the Objective of the Project Planning Process? Objective of the Project Planning Process : To provide framework that enables manager to make reasonable estimates of resources, cost and schedule. 56. What are the Objectives of Requirement Analysis ? Objectives of Requirement Analysis : Describe what customer requires Establish a basis for creation of software design Define a set of requirements that can be validated once the software design is built 57. What are the Requirements Engineering Process Functions? Inception Elicitation Elaboration Negotiation Specification Validation Management 58. What are the s/w risk components? Performance risk. Cost risk. Support risk. Schedule risk. 59. List out the uses of PERT and CPM. Determines the critical path. Establish the most-likely time estimates for individual tasks. Calculate boundary times that define time-window for a particular task. 60. What is a time-line chart or Gantt chart? Time-line chart or Gantt chart is a graphical representation of project schedule. The chart shows the start and end time of each project task and their dependencies. It is a chart listing the various work tasks ,the duration of each tasks and associated milestones It can be developed for the entire product or for a product 61. Define Activity and Milestone.

Activity is a part of the project that takes place over a period of time. Milestone is the completion of an activity a particular point in time.

62. Compare the organizational structure.

Highly Structured High certainty Loosely Structured Uncertainty
SEC/IIICSE/SE

 Repetition Large Projects

New techniques or technology Small Projects

63. What is a risk?

A risk is an unwanted event that has negative consequences. 64. List out the steps in Risk Analysis and Management. Risk Identification Risk Estimation Risk Assessment Risk Management and Monitoring Risk Refinement 65. What is project tracking? Project tracking is a consequent activity which monitors the progress of a project related to the schedule made. It aims to find the error and deviation from schedule if any.

66. What is the critical distinction between a milestone and deliverables?

Milestone Represents the end of a distinct logical stage or a activity of the project. Internal project results presented to managers. Milestones need not be a deliverables. Deliverables Represents the end of major phase of the project. presented to customer. Deliverables are usually milestones.

67. How does the project tracking accomplished? To accomplish tracking, there are a number of ways as given below: Conduct periodic project status meeting with team members. Determine whether formal project mile stones are accomplished by scheduled date. Informal meeting with practitioners to obtain their assessment. Using earned value analysis. Comparison between planned with actual 68. What is project scheduling? It describes the s/w development cycle for a particular project by enumerating the phases or stages of the project and breaking each into discrete tasks or activities to be done. Project scheduling is an activity that distributes estimated effort across planned project duration, by allocating the effort to specific software engineering tasks. 69. List the standards and methods in the project plan. o Algorithms o Tools o Review or inspection techniques o Design language or representations o Coding languages o Testing techniques 70. List the common milestones in the software development process.
SEC/IIICSE/SE

Life- cycle objectives Life- cycle architecture Initial operational capability

71. Define: Precursor, Due date, Duration, Endpoint. Precursor: It is event or set of events that must occur in order for an activity to start. Duration: Length of time needed to complete an activity. Due date: Data by which an activity must be completed Endpoint: is a milestone or deliverables.

72. List the effort estimation methods. Top-Down or bottom-up analysis. Analogy process. Delphi technique Wolveton model using cost matrix 73. List the work styles. Extroverts: tell their thoughts Introverts: ask for suggessions Intuitives: base decisions on feelings Rationals: base decisions on facts, options 74. Define effort estimation. Estimating project costs is one of the important aspects of project planning and management. Estimating cost has to done as early as possible. 75. What are the strategies used for risk reduction. o Avoiding the risk o Transferring the risk o Assuming the risk

PART B
Explain Agile Methods with examples. Explain the Wassermans Discipline of Software Engineering. Explain the Operational Specification model Discuss about static and dynamic modeling in detail with example. Explain the items include Project Plan in detail. What is Risk Management and explain the steps in risk management. Explain the concepts of project personnel in detail. Write short notes on i) Requirements Process ii) Requirements Elicitation 9. Explain the concepts of Requirement Engineering process. 10. Explain the prototyping approaches in detail with their applications.
SEC/IIICSE/SE

1. 2. 3. 4. 5. 6. 7. 8.

11. Explain the various requirement elicitation techniques.

12. Explain the Entity relationship diagram(ERD) with some suitable example.

13. Describe how software requirements are documented? State the importance of
documentation. 14. How we organize the staff for a project? 15. Explain the concepts of Validation and Verification. 16. Explain the different Effort estimation techniques. i)Expert Judgment ii)Algorithms Methods 17. Draw and explain the data flow diagram (DFD) and Entity- Relationship Diagrams for the Payroll System.

SEC/IIICSE/SE