Scribd
Upload
1K views

SE Reviewc

The document contains review questions from past exams covering several chapters on software engineering topics. It includes questions about software and hardware characteristics, software evolution, process models, agile development principles, requirements engineering, system modeling, data modeling, object-oriented concepts, project planning, scheduling, and networking. Sample questions assess definitions, methodologies, modeling techniques like UML diagrams and ER diagrams, and computing project metrics.

Uploaded by

Ron Jefferson
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
1K views

SE Reviewc

The document contains review questions from past exams covering several chapters on software engineering topics. It includes questions about software and hardware characteristics, software evolution, process models, agile development principles, requirements engineering, system modeling, data modeling, object-oriented concepts, project planning, scheduling, and networking. Sample questions assess definitions, methodologies, modeling techniques like UML diagrams and ER diagrams, and computing project metrics.

Uploaded by

Ron Jefferson
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

REVIEW (Taken from past exams) Chapter 1 - Test Questions (Software Engineering) 1.

How does software differ from the artifacts produced by other engineering disciplines? 2. How do software characteristics differ from hardware characteristics? 3. Explain what is wrong with the notion that computer software does not need to evolve over time. 4: Definitions Computer Engineering, Software Engineering,. Software Engineering, Software Process,COCOMO, Requirement,Failure,e tc. Chapter 2 - Test Questions (Process and Process Models) 1. List three areas in which process models may differ from one another. 2. Explain why systems developed as prototypes should not normally be used as production systems. 3. Describe the phases of the prototyping model for software development? 4. Describe the role of risk analysis in evolutionary process models like the spiral model. 5..Why are incremental process models considered by many to be the best approach to software development in a modern context? Chapter 2-4 Test Questions (Agile Development, ) Requirements Engineering & System Modeling 1. List the key issues stressed by an agile philosophy of software engineering. 2. Explain how the principles underlying agile method lead to the accelerated development and deployment of software. 3. Describe the role of customers and end-users on an agile process team? 4. Describe the three key assumptions regarding software projects that every agile software process must address. 5 . What are the six steps for requirements engineering?

6. Show an example of using a UML diagram. 7. Understand Risk Management in a software project. Chapter 4- Test Questions 1. What are the data modeling elements represented in the entity relationship diagram (ERD)? 2. Describe the general process of creating a data flow diagram (DFD). 3. Draw a DFD of receiving money from an ATM. 4. Explain why encapsulation, inheritance, and polymorphism are three important characteristics of object-oriented systems. 5.. The department of public works for a large city decided to develop a Web based pothole tracking and repair system (PHTRS). From The PHTRS scenario construct the Entity Relationship diagram. (a) List the different Entities. (b) For each two entities that are related - write the names of the Entity types in the boxes; label the relationship phrase and define the cardinalities (1:1;1:M;M:M) of the Relationship type. The PHTRS Citizens can log onto a Web site and report the location and severity of potholes. As potholes are reported they are logged within a public works department repair system and are assigned an identifying number, stored by street address, size (on a scale of 1 to 10), location (middle, curb, etc), district (determined from street address), and repair priority (determined by the size of the pothole). Work order data are associated with each pothole and includes pothole location and size, repair crew identifying number, number of people on crew, equipment assigned, hours applied to repair, hole status (work in progress, repaired, temporary repair, not repaired), amount of filler material used and cost of repair (computed from hours applied, number of people, material and equipment used). Finally, a damage file is created to hold information about reported damage due to the pothole and includes citizen s name, address, phone number, type of damage, dollar amount of damage. PHTRS is an on-line system; all queries are to be made interactively. Chapter 2. Test Questions (Project Planning Concepts) 1. List 3 principles for scheduling software projects. 2. In software project scheduling work, what is a task (or activity) network? 3 . Show the differences between the COCOMO and COCOMO II models. Given the COCOMO formulas be able to compute the Effort, etc.

4. Why is CPM/PERT a popular and widely applied Project Management technique? 5. What is the critical Path, and what is its importance in project planning? 6.Given the following network with activity times in months and (a-b) represents the flow from a to b. In example 1-2 shows the flow from 1 to 2, etc. Indicate the Earliest times, Latest times and slack for each node. Identify the Critical Path. Activity 1.2 1-3 1-4 2-5 2-6 3-5 4-5 4-8 5-7 5-8 8-7 6-9 7-9 Time (months) 8 6 3 0 5 3 4 2 7 4 0 4 8

7. Multiple choice in OO concepts.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy