COIS 3030H Study Guide - Fall 2018, Comprehensive Midterm Notes - System Context Diagram, Waterfall Model, Trust Law
12 Oct 2018
School
Department
Course
Professor
COIS 3030H
MIDTERM EXAM
STUDY GUIDE
Fall 2018
WEEK 1 LEC NOTES
COIS 3030
Monday, September 10, 2018
(LECTURE 2)
**This course is about software requirement specifications, not coding.
Dependability
• Consequences of systems failing
• Annoying to catastrophic
• Opportunities lost, businesses failed, security breaches, systems destroyed, lives lost
• Very important characteristic for good and sound software
Software development process
• A well-defined and well managed software engineering process
• Provides guidance as to the order of a teams activities
• Specifies what artigacts should be developed
• Directs the tasks of individual developers and the team as a whole
• Offers criteria for monitoring and measuring a projects products and activities
Software Process Activities
**Primary Activates (Focuses on the development activitie)
• Development
• Operation
• Maintenance
Supporting Activities
• Documentation
• Configuration management
• Quality assurance
• Verification and validation
• Training
Process -Related Activies
• Management
• Tailoring
find more resources at oneclass.com
find more resources at oneclass.com
Classic Waterfall Model
1. Requirements Elicitation (Why you want to develop)
a. Discover functionality, user expectations, Non-functional requirements and qualities
2. Specification and Analysis (What)
a. Produce a complete and unambiguous description of the problem domain and the
requirements
3. Architecture Design (How)
a. Elaborate a system architecture that fulfils the requirements
b. Designing the overall architecture of the system
4. Detailed Design (how exactly)
a. Allocate responsibilities to modules
b. Design how functionality is achieved at run time
c. Noally use UML diagas to coplete this class, seuece, actiity…
5. Implementation
a. Elaborate low level algorithms
b. Implement your modules
Software Development V Model
-Focuses on testing
Production Phase
1. Requirements Elicitation
2. Requirement specification and analysis
3. Architecture Design
4. Detailed Design
5. Implementation
Assembly Phase
6. Unit Testing (Make sure the code is free of bugs)
7. Component Testing
8. Integration Testing
9. System Testing
10. System in Use
Ipotace of Good Reuieets
• Faults/omissions made at the requirement stage are expensive to fix later
• Stated requirements might be implemented, but the system is not one that the customer wants
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
**this course is about software requirement specifications, not coding. Dependability: consequences of systems failing, annoying to catastrophic, opportunities lost, businesses failed, security breaches, systems destroyed, lives lost, very important characteristic for good and sound software. **primary activates (focuses on the development activitie: development, operation, maintenance. Supporting activities: configuration management, quality assurance, verification and validation, training. I(cid:373)po(cid:396)ta(cid:374)ce of (cid:862)good(cid:863) re(cid:395)ui(cid:396)e(cid:373)e(cid:374)ts: faults/omissions made at the requirement stage are expensive to fix later, stated requirements might be implemented, but the system is not one that the customer wants. Identify and resolve risks: development and test, plan the next iteration, risk-d(cid:396)i(cid:448)e(cid:374) p(cid:396)ocess: it"s a p(cid:396)ocess that puts high e(cid:373)phasis o(cid:374) (cid:396)isk (cid:373)a(cid:374)age(cid:373)e(cid:374)t, benefits: risk reduction, functionality can be added incrementally, software produced early. Something the product must do to support its o(cid:449)(cid:374)e(cid:396)"s business. Production phase: requirements elicitation, requirement specification and analysis, architecture design, detailed design. Assembly phase: unit testing (make sure the code is free of bugs, component testing.
