Busy. Please wait.

show password
Forgot Password?

Don't have an account?  Sign up 

Username is available taken
show password


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.

Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove Ads
Don't know
remaining cards
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
restart all cards

Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

Development Process

The classic software development phases and expressions

Analysis An activity during which developers ensure that the system requirements rea correct, complete, consistent and unambiguous. Analysis produces an analysis model.
System Design developers define the system design model, design goals of the project, and decompose the system. -selection of the hard,software platform, persistent data management strategy, global control flow, access control policy and boundary condition strategies.
System Lifecycle
A requirement a condition or capability to which a system must conform
FURPS+ Functionality, Usability, Reliability, Performance, Supportability The ”+” in FURPS+ reminds you to include such requirements as: Design constraints, Implementation requirements, Interface requirements, physical requirements
System design model High-level description of the system -design goals, subsystem decomposition, hardware/software platform, persistent storage strategy, global control flow, access control policy, boundary condition strategies-,Strategic decisions made by the architectTeam
SDD System Design Document describing the system design model.
System Model The set of all models built during development to reason about the system. The system model includes the analysis model, the system design model, the object design model and the source code.
Boundary Condition A special condition the system must handle. Boundary conditions include start-up, shutdown, and exceptions.
Analysis Model A model of the system that aims to be correct, complete, consistent, and unambiguous. The analysis model consists of the functional model, the analysis object model, and the dynamic model.
Object Design Model
Analysis Object Model The object model produced during analysis. The analysis object model describes the application domain concepts that the system manipulates and the user-visible interfaces of the system.
Functional Model Describes the functionality of the system from the user’s point of view. In this book, we represent the functional model with use cases.
Dynamic Model Describes the components of the system that have interesting behavior. In this book, we represent the dynamic model with state machine diagrams, sequence diagrams, and activity diagrams.
Object Design Model A detailed object model representing the application and solution objects that make up the system. The object design model includes detailed class specifications, contracts, types, signatures, and visibilities for all public operations.
ODD Object Design Document - A document describing the object design model. The object design model is often generated from comments embedded in the source code.
Robustness The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environment conditions.
Software Life Cycle All activities and work products necessary for the development of a software system.
Software Life Cycle Model An abstraction representing the development of software for the purpose of understanding, monitoring, or controlling it. Examples include the waterfall model, the V-model, Boehm’s spiral model, the Unified Process, and the issue-based life cycle model.
Risk Management A management method for identifying and addressing areas of uncertainty before they negatively affect the schedule of the project or the quality of the system.
Created by: timeakiss