Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
26 Cards in this Set
- Front
- Back
|
Software Crisis
|
Increase in program size and complexity Time and cost slippage Failure at customer site Untraceable errors after delivery Difficulty in maintenance |
|
|
SE problems
|
Business demand defect free software adherence to timelines and budget. Software development needs engineering approach. |
|
|
SE
|
application of systematic disciplined quantifiable approach to development operation and maintenance of software. produce quality software. includes methods, tools, and procedures which are models of Soft ware development. |
|
|
Engineering Process
|
Processes-Sequence of activities need to produce the system. Methods- Dev. approach for expected quality outputs adhering time and time Tools- Provide support for executing processes |
|
|
SE
|
Processes-Requirement Development, Software Development, Software Design, Development, Testing Methods- Structured and Object Oriented methods Tools- Design, Coding, and Testing tools |
|
|
Process
|
sequence of steps executed for a given purpose every step there are inputs and outputs processes may have sub-processes road map that helps to create a timely, high quality result |
|
|
Process Adherence
|
Usable outputs no re-work or less rework Profitable as cost was as per expectations happy client repeat business |
|
|
Non Adherence
|
opposite
|
|
|
Software Process model
|
(SDLC) ex Waterfall, Prototyping. Spiral model |
|
|
SDLC phases
|
Requirement Dev. Design Construction Testing |
|
|
Requirements Development Activities
|
Elicitation-Identification of user req. Analysis- Classification of Analysis Specification- Documentation of req. Verification-Validation of req. |
|
|
Requirement Elicitation
|
seeking, discovering, acquiring and elaborating understanding the needs of users communication centric and iterative (Interview, Questionnaire, prototyping, Task analysis, Brainstorming) |
|
|
Requirement Analysis Classification
|
Function req.-Business needs Non-Fun req Product- Reliability, Usability, Portability, Security |
|
|
Efficiency
|
Performance and Space
|
|
|
Organizational
|
Delivery and Budget
|
|
|
Software Requirement Specification (SRS)
|
Formal doc containing req which developers should design and implement. Captures both Functional and non- functional req. Intended for diverse set of stakeholders including the senior management.
|
|
|
Requirement Verification
|
(Quality Attributes) Necessary Concise Unambiguous Consistent Complete Identifiable Traceable Testable Implementable |
|
|
Necessary
|
meet the user needs of the system
|
|
|
Concise
|
clearly using simple words |
|
|
Unambiguous
|
interpreted in only one way |
|
|
Consistent |
do not conflict with other req. |
|
|
Complete |
provides all necessary info. |
|
|
Identifiable |
be identified using and unique identifier |
|
|
Traceable |
traced to its origin |
|
|
Testable |
ensured as implemented in system |
|
|
Implementable |
|
