CSS 360 Midterm Exam

Code and Fix(Agile) Correct answer- Build first version Modified until satisfied Operations Mode Retirement Waterfall(Prescriptive) Correct answer- System Requirements Software Requirements Analysis Program Design Coding Testing Operations Sashimi (Prescriptive) Correct answer- (Waterfall Variant) Addresses the problem that each phase must be complete before proceeding to the next phase. Tackles this problem by having overlapped phases Staged Delivery(Prescriptive) Correct answer- (Waterfall Variant) Concept Analysis Design [Coding Test Delivery](Repeated) Spiral(Prescriptive) Correct answer- (Waterfall Variant) Developed to accessed risk of project(For both prototypes/formal projects) Evolutionary Prototyping(Neither) Correct answer- Concept Design and Implement Refine Release Kanban(Agile) Correct answer- A production control system eXtreme Programming XP(Agile) Correct answer- Pair Programming , Customer Participation , Code Standards , 40 hour work week Scrum(Agile) Correct answer- Backlog Sprint Meeting Unified Process(Prescriptive) Correct answer- Uses : Timebox Iterations , cohesive architecture , re-using existing components , visual modeling. Manage requirements and change. DSDM(Agile) Correct answer- Dynamic Systems Development Method. Focus on the business need , deliver on time , collaborate , never compromise quality , build incrementally from firm foundations , develop iteratively , communicate continously and clearly , demonstrate control. LCO Correct answer- Life Cycle Objectives LCA Correct answer- Life Cycle Architecture Spiral into Waterfall (Prescriptive) Correct answer- (Waterfall variant) Address risks while following a waterfall model Agile Developers Correct answer- More ownership of the project , collocated , collaborative Prescriptive Developers Correct answer- Plan-driven , adequate skills , access to external knowledge. Agile Customers Correct answer- Dedicated , collocated , collborative , representative customers Prescriptive Customers Correct answer- Access to collaborative representative customers. Agile Requirements Correct answer- Largely emergent , rapid change Prescriptive Requirements Correct answer- Knowable early , largely stable Agile arcitecture Correct answer- Design for current requirements Prescriptive Architecture Correct answer- Design for current and foreseeable requirements Agile refactoring Correct answer- Inexpensive Prescriptive refactoring Correct answer- expensive Agile Size Correct answer- 50 people or less| Size of 20 is difficult to coordinate Prescriptive Size Correct answer- Larger Agile objective Correct answer- Rapid Value Prescriptive Objective Correct answer- high assurance 4 essential problems Correct answer- Complexity , Conformity , Chageability , Invisibility Complexity Correct answer- No two software parts are alike Conformity Correct answer- Software must confirm to the existing environment Changeability Correct answer- Software is under pressure to change Invisibility Correct answer- Software is invisible and unvisualizable Analysis Correct answer- Gathering of stakeholder requirements Stakeholder Correct answer- Anyone or group with a vested interested in the succcess of the project(Customer , Users , Information providers , IT , consumers , Operations , Quality Assurance) Life Cycle Phases Correct answer- Requirement , Architecture/Design , Implementation, Testing , Maintanence Requirements Analysis/Engineering Correct answer- Activity of unearthing customer needs feasability study Correct answer- decides whether or not the proposed system is worth while. feature creep Correct answer- uncontrolled or unmanaged process of addiditions. Commonly causes project failure. Functional Requirements Correct answer- describe the functionality or services that the system is expected to provide. Non-functional Requirements Correct answer- requirement that is not directly concerned with specific functions. Constraints Correct answer- Limitations on the design or on the project itself(Budget , Schedule, Technology) Deliverables Correct answer- Maybe in a form of a requirements document. Requirements Management Correct answer- The process of managing changing requirements during requirements engineering process and system development. Enduring Requirements Correct answer- stable requirements derived core activity of customer. Volitile Requirements Correct answer- requirement that change during system development. Traceability Correct answer- relationships between requirements , sources , and system design. Product Backlog Correct answer- Requirements. Usually represented as user stories. User Stories Correct answer- Consists of Card, Conversation , and Confirmation. Cards Correct answer- Stories are tradditionally written on cards Conversation Correct answer- Details behind story.