asdsdf sdf
Function points
COTS measure the role of correlation in observational studies and the criteria for causality.
Reliability -> consistency: Trained personnel, scales
Measurement – product and process.
620
Tutorial for programmers, primer to objects
Q.
-Agile process -> requirements document ready, how do you move forward? Customer feedback important and risks, agile? Empirical process
-Homework due?
-Final exam paper?
Assignment 1: detailed. Detailed diagrams and descriptions (prof. prefers diagram, larman says description)
Use case model only includes functional requirements (not logging use case, one step fine). Excluded: non-functional, performance req., no human steps, interaction with system
Emphasis on covering all requirements and not break use case rules
Check Lists for Use Case Documentation
1) Does each primary use case have a use case description?
2) Does each use case have one primary scenario, one or more variations of successful scenarios, and failure scenarios identified?
3) Are scenarios detailed enough to visualize the steps of the scenario?
4) Is each step of a use case description conceptually only one step that can be logically done together? (e.g., „search customer and add their data‟ must be split because they cannot be done together in one step.)
5) Is each step specific? (e.g., „add customer data‟ is not specific) Can you visualize each step?
6) Are preconditions those that need to be true before the execution of the use case?
7) Are post-conditions written in past and passive form?
8) Are all post-conditions identified?
9) Did you identify all the objects that need to be created or deleted?
10) Did you identify all the attributes that need to change their values?
11) Did you identify all the associations that need to be connected or disconnected between objects
12) Does each included use case or extending use case have its own use case description?
13) Are there any duplicate use cases or
COTS measure the role of correlation in observational studies and the criteria for causality.
Reliability -> consistency: Trained personnel, scales
Measurement – product and process.
620
Tutorial for programmers, primer to objects
Q.
-Agile process -> requirements document ready, how do you move forward? Customer feedback important and risks, agile? Empirical process
-Homework due?
-Final exam paper?
Assignment 1: detailed. Detailed diagrams and descriptions (prof. prefers diagram, larman says description)
Use case model only includes functional requirements (not logging use case, one step fine). Excluded: non-functional, performance req., no human steps, interaction with system
Emphasis on covering all requirements and not break use case rules
Check Lists for Use Case Documentation
1) Does each primary use case have a use case description?
2) Does each use case have one primary scenario, one or more variations of successful scenarios, and failure scenarios identified?
3) Are scenarios detailed enough to visualize the steps of the scenario?
4) Is each step of a use case description conceptually only one step that can be logically done together? (e.g., „search customer and add their data‟ must be split because they cannot be done together in one step.)
5) Is each step specific? (e.g., „add customer data‟ is not specific) Can you visualize each step?
6) Are preconditions those that need to be true before the execution of the use case?
7) Are post-conditions written in past and passive form?
8) Are all post-conditions identified?
9) Did you identify all the objects that need to be created or deleted?
10) Did you identify all the attributes that need to change their values?
11) Did you identify all the associations that need to be connected or disconnected between objects
12) Does each included use case or extending use case have its own use case description?
13) Are there any duplicate use cases or