TERNINAL TEST 1 (2 marks)

1. What are basic process activities that are applicable to all software processes? 1) Software specification: The software must define functionality of the software and constraints on its operation. 2) Software development: The software must be developed according to its specification. 3) Software validation: The software must perform all the function that customer wants. 4) Software evolution: The software must develop to meet changing customer requirements.

2. What is System Engineering? System Engineering means designing, implementing, deploying and operating systems which include hardware, software and people. 3. Define Verification and Validation. Verification Ensuring that your product meets the original design. You build the product right Internal viewpoint Validation Ensuring that your product design satisfies its intended use. You build the right product - External viewpoint. . 4. Define CASE tool. CASE-Computer Aided Software Engineering. CASE tools are computer based tools to assist in the software engineering process. CASE tool is made up of set of tools. 5. What are inputs given to the technical review process? Statement of objectives. Software elements being examined. Specifications for the software elements. Plans, standards or guidelines against which the software elements are to be examined. 6. What are the different phases in Software Development Life Cycle (SDLC)? Strategy planning Feasibility study Analysis Design Implementation Maintenance 7.Difference between system and software engineering. system It deals with aspects of computer based system development. In system engineering the overall objective of the system must be defined. In the system engineering the role of hardware, software,people, database, procedures and other system elements must be identified. software Software engineering is a part of system engineering The Software engineering is concerned with the practical problems of producing software.

8. What are the attributes of good software? The software should deliver the required functionality and performance to the user. Maintainability Software must evolve to meet changing needs. Dependability Software must be trustworthy. Efficiency

 Software should not make wasteful use of system resources. Usability Software must be usable by the users for which it was designed.
9. 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.

10. 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. 11. 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 12. 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. 13. 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. 14. 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. 15. What are the benefits of prototyping? a. Prototype serves as a basis for deriving system specification. b. Design quality can be improved. c. System can be maintained easily. d. Development efforts may get reduced. e. System usability can be improved. f. 16. What are the characteristics of SRS? g. Correct The SRS should be made up to date when appropriate requirements are identified. h. Unambiguous When the requirements are correctly understood then only it is possible to write unambiguous software. i. Complete To make SRS complete, it should be specified what a software designer wants to create software. j. Consistent It should be consistent with reference to the functionalities identified. k. Specific The requirements should be mentioned specifically. l. Traceable What is the need for mentioned requirement? This should be correctly identified.

17. State the four generic activities of requirement engineering? Requirement engineering involves four generic activities such as: 1. 2. Feasibility study Requirements Elicitation and Analysis

3. Requirements specification and documentation 4. Requirements validation 5. 18. 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 19.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. 20.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

21.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. 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.

22.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 23. List out the steps in Risk Analysis and Management. Risk Identification Risk Estimation Risk Assessment Risk Management and Monitoring Risk Refinement

24. 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

25. List the standards and methods in the project plan. o o o o o o Algorithms Tools Review or inspection techniques Design language or representations Coding languages Testing techniques

26. List the work styles. Extroverts: tell their thoughts Introverts: ask for suggessions Intuitives: base decisions on feelings Rationals: base decisions on facts, options

27. 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