CSC 216 Lecture Notes - Lecture 9: Code Coverage, User Story, List Of Fables Characters

117 views5 pages
15 Sep 2016
School
Course
Professor

Document Summary

Software artifacts: any document, file, or tangible creation related to the software or its creation or maintenance. Goal: to understanding customer requirements for the software system. Very difficult to get right the first time. Requirements may evolve over the course of developing a software system. Artifacts: requirement documents, use cases, user stories: design. Goal: to decide the structure of the software and the hardware configurations that support it. How individual classes and software components work together in the software system. Medium programs: 1000s of classes and interfaces. The design for single user applications differs from that of web and mobile applications. Artifacts: design documents, class diagrams, other uml diagrams: implementation/code. Goal: to translate design into a concrete system. Can use any language, but some languages are better suited to certain types of programs than others. Artifacts: source code, documentation, configuration files, media, executables, bug database, source code, repository: testing. Goal: to execute software with the intent of finding errors.

Get access

Grade+
$40 USD/m
Billed monthly
Grade+
Homework Help
Study Guides
Textbook Solutions
Class Notes
Textbook Notes
Booster Class
10 Verified Answers
Class+
$30 USD/m
Billed monthly
Class+
Homework Help
Study Guides
Textbook Solutions
Class Notes
Textbook Notes
Booster Class
7 Verified Answers

Related Documents