User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
A. User Action Notation
Application Domain
Staff stability
Programming language
External environment
Failure detection
Damage assessment
Fault avoidance
Fault repair
Internet Explorer
Mozilla
MS-Office
Oracle
Class Name
Entity
Attributes
Service
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
Waterfall model
Incremental model
Spiral model
Iterative model
major decision points are tested early
no drivers need to be written
no stubs need to be written
regression testing is not required
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
ensure that their products only meet the SRS.
act consistently with the public interest.
act in a manner that is in the best interests of his expertise and favour.
none
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
bottom-up
random
top-down
center fingring
licensing
responsiveness
processing time
memory utilization
70 to 80
30 to 40
50 to 60
10 to 20
Polymorphism
Encapsulation
Inheritance
Information hiding
Understanding
Restrictions
Transparency
Controversy
Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
The product should be easy to use.
It means that the product designed /created should be easily available.
Software engineers shall ensure that their products and related modifications satisfy the client.
Profit maximization
Cost reduction
Customer satisfaction
All of the above
Large system applications
Small system applications
Medium system applications
Very small system applications
Software Analysis
Software Design
Software quality
Software testing
interface design
data design
procedural design
architectural design
Ability to deliver software on time with good quality
A situation in which experienced developers leave the company
Inability of new software to inter-operate with existing software
Instability in the development team
Minimization, Satisfaction
Minimization, Dissatisfaction
Maximization, Satisfaction
Maximization, Dissatisfaction
Identify system- processing transformation
Identify input transformation
Identify output transformation
All the above
Waterfall
Spiral
Iterative
Cleanroom
Entity- relation model
Data flow model
Structural model
Object model
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Accounting Personnel
Database Manager
Salesman
System Operator
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
An Old Fashioned model that cannot be used in a modern context
A good approach when a working program is required quickly
A useful approach when a customer cannot define requirements clearly.
A reasonable approach when requirement are well defined.