/ 7 = 3.5714 per quiz. § 6 Assignments: 25 / 6 = 4.1666 per assignment. We are still reviewing a couple of Academic Integrity cases. I will be in touch during the weekend. § Midterm Exam: 25% i.e., your current grade / 4 § Final Exam: on Monday A curve is a possibility but not guaranteed. If applied, it will be applied to everyone; it is NOT case-based.
(Wi) Very Low Low Nominal High Very High Extra High Precedentedness (PREC) thoroughly unprecedented largely unprecedented somewhat unprecedented generally familiar largely familiar throughly familiar Development Flexibility (FLEX) rigorous occasional relaxation some relaxation general conformity some conformity general goals Architecture/Risk Resolution (RESL)* little (20%) some (40%) often (60%) generally (75%) mostly (90%) full (100%) Team Cohesion (TEAM) very difficult interactions some difficult interactions basically cooperative interactions largely cooperative highly cooperative seamless interactions Process Maturity (PMAT) Weighted average of “Yes” answers to CMM Maturity Questionnaire * % significant module interfaces specified, % significant risks eliminated
Project Factors 4.1. Use of Software tools (TOOL) 4.2. Multisite development (SITE) 4.3. Required schedule - stretch-out or acceleration (SCED) Multisite development
LOC § Nothing to be reuse § What could be its cost in the best-case scenario? § What could be its cost in the worse-case scenario? § What is the best-case scenario? (value for the factors) § What is the worse-case scenario? (value for the factors)
paper where you describe and include COCOMO reports for the PacMan videogame: § It has 1200 LOC § Nothing to be reuse § What could be its cost in the best-case scenario? § What could be its cost in the worse-case scenario? § What is the best-case scenario? (value for the factors) § What is the worse-case scenario? (value for the factors) 2. Do the same for another project – a project that you create in the past (a capstone project, a Summer internship, a personal project, etc. ). You do not need to share the code, just describe what the project is about and the LOC numbers, reuse or not, etc. Your paper should include (A) description of the system (B) COCOMO reports (two reports per system); (C) your conclusions about the usefulness / correctness of the values reported
Replace the Draw the Use Case Diagram for: § A product backlog § Activity and State Diagrams for an Authentication process § A set of tasks for one of the features (or requirements) included in the described scenario
Independent – loosely coupled with one another § Negotiable – Stories are what and why , not how ( 99% ). § Valuable – for the customer! § Estimatable – Effort/Cost of design, build, and test. § Small (sized appropriately) § Testable – pass or fail
case by providing § a graphical representation of the flow of interaction. Create an activity diagram for each use-case. § a list of the different states of a system. Build a state diagram for the system. They are not mandatory and they can be combined.
Name < the name is the goal as a short active verb phrase> Goal / Description < a longer statement of the goal in context if needed > Pre-conditions <what we expect is already the state of the world> Success End Condition <the state of the world upon successful completion> Failed End Condition <the state of the world if goal abandoned> Actors <a role name or description for the primary actor> <other systems relied upon to accomplish use case> Trigger <the action upon the system that starts the use case> Description step action 1 <put here the steps of the scenario from trigger to goal delivery, and any cleanup after> 2 <...> 3
for Game of Life rules § State machine diagram for an Assignment on Canvas § Use case diagram for your operating system § State machine diagram for a webpage (URL) on your browser § Activity diagram for enrollment on a new course on MyASU
… Z B time epics Epic or Story • Does it seem difficult to estimate? • Does it seem complex? • Is it long? • Are there technical or business unknowns that are unclear?
Software Size (Lines of Code) 2. Software Scale Drivers: sources of exponential effort variation 3. Software Cost Drivers: sources of linear effort variation. They group in 4 categories: product, platform, personnel and project Factor are rated between very low and very high per rating guidelines
javiergs@asu.edu Fall 2021 Copyright. These slides can only be used as study material for the class CSE563 at ASU. They cannot be distributed or used for another purpose.
javiergs
ohbarye
tbsten
algoartis
ypresto
nrslib
tomohisa
thousanda
rkaga
ike002jp
tchov
shota_tech
cp20
andyhume
hannesfritz
rocio
scottboms
jakevdp
sugarenia
kneath
honnibal
stephaniewalter
swwweet
cassininazir
ammeep
