Download SOEN 341 Midterm Practice Test: Software Engineering Concepts and Models and more Exams Software Engineering in PDF only on Docsity!
SOEN 341 Midterm Practice Test
With Correct Answers
6 Phases of waterfall method - ANSWER 1. Requirements
- specification
- Design
- Implementation
- Testing
- Maintenance
Explain waterfall model - ANSWER - Is an incremental development
- Base on documents
- Requirement analysis yields a requirement document
- Design is based on the requirement doc
- Fixed milestone at the end of each stage
- each process feed the next 0ne without further interaction
You have to finish each stage before going to the next one
Problem of waterfall model - ANSWER - By the time the first line of code is written a lot of work has been done
- Mistake in early phases are very hard to correct
- No allowance for prototyping
- Customer cannot use anything until the system is complete
- Implies that once the project is done, all you have to do is maintnance
Spiral process - ANSWER Explicitly embrace prototyping and an iterative approach
- Start by developing a small prototype
- Follows a mini waterfall that serves to get requirements
- Last stage is review of the first prototype
Spiral model (more) - ANSWER Each phase starts with a design goal and ends with the client reviewing the progress thus far.
It is intended for large, expensive, and complicated projects.
Spiral process advantage over waterfall - ANSWER - Before each end of cycle a review, customer discuss their experience
- Has risk analysis, before each new loop they decide what are the major
customer representative.
Scrum - ANSWER is an iterative incremental framework for managing complex work (such as new product development) commonly used with agile software development.
Sprint - ANSWER In scrum, team creates potentially shippable prodruct increment
Daily scrum - ANSWER fast 15 mins meeting. What did you do yester? what you planing to do today? what are the problem you have encounter?
Sprint backlog - ANSWER contain information about how the team will implement the feature for the upcoming sprint
PSP - ANSWER Personal software process
is a structured software development process that is intended to help software engineers better understand and improve their performance by
tracking their predicted and actual development of code.
Use case components - ANSWER Represent a class of functionality provided by the system.
- Unique name
- Participating actors
- entry conditions
- exit conditions
- Flow of events
- Special requirements
Scenario - ANSWER An instance of a use case
Use case Relations - ANSWER Extends: represent seldom invoked use cases or exceptional functionality
Includes: functional behavior common to more than one use case
Inclusions use case - ANSWER - express commonlality between several different use cases
- are included in other use cases: enable to avoid repeating details in multiple
They do not appear in instance diagrams at all.
Aggregation - ANSWER Special associations that represent parts. like. Like region is part of a country
Composition - ANSWER Strong kind of aggregation. If the aggregation is destroyed, the parts are destroyed as well
Interfaces - ANSWER Describe a portion of the visible behaviour of a set of objects
Creating class diagram - ANSWER -Identify a first seto fc andidate classes -Add associations and attributes -Find generalizations -List the main responsibilities of each class -Decide on specific operations -Iterate over the entire process until the model is satisfactory
Synchronous message - ANSWER Has a filled in arrow
Interaction diagram - ANSWER you should draw class diagram and use case model before.
lifeline in sequence diagram - ANSWER Attached to each object or actor
activation box in sequence diagram - ANSWER during the period of time that object is performing computations. the object is said to have live activation during these times
System sequence diagram vs sequence diagram - ANSWER System sequence diagram: Visualizes a use case. Participants that are exchanging messages are actors and systems.
Sequence diagram: exchange between objects ( instances of various classes) the message exchanged are method invocation
When use cases are written - ANSWER During design and testing phases.
What cannot be specified by used cases? - ANSWER Time fixed process. System that are not a direct consequence of use actions.
