CSE360 Introduction to Software Engineering Lecture: Requirements Engineering II Javier Gonzalez-Sanchez [email protected] javiergs.engineering.asu.edu Office Hours: By appointment
Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 2 Fall 2021 | 00000001 Final Project (Part A) Use your project 3 as starting point. If you did not finish it. Work on It. 1. GitHub – Code. Include TA as team member 2. Astah – UML Diagram 3. Junit - Test Cases for K-means and Nearest Neighbors 4. Software Metrics: LOC, eLOC, lLOC, CC, D 5. Taiga – BackLog, Burndown Chart. Include TA as team member
Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 4 Fall 2021 | 00000001 INVEST in good requirements • 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
Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 9 Fall 2021 | 00000001 Team • Team makes decisions • Team is measured constantly • Motivated Individuals. • With Self-Organizing Capabilities. • Technically competent
Javier Gonzalez-Sanchez | CSE360 | Summer 2018 | 23 Fall 2021 | 00000001 Case 1 • Features (Stories) (for this project, almost sure no epics) • Technical Work • Knowledge Acquisition • Defects, not yet (starting the project)
CSE 563 Software Requirements and Specification Javier Gonzalez-Sanchez, Ph.D. [email protected] 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
ivargrimstad
mski_iksm
iwaken71
kazutan
dicoding
aanrii
taclose
fendo181
bastnic
gpsnmeajp
yusukebe
hollycummins
afnizarnur
ddemaree
62gerente
shpigford
roundedbygravity
paulrobertlloyd
rmw
jcasabona
destraynor
mthomps
sstephenson
andyhume