Meeting 2: (Modules 1–2) Introduction to the software development life cycle and the role of requirements analysis.
Assignment 2a due at 23:59: Draft requirements document.
Meeting 3: (Module 2) Feedback on your draft requirements documents, and an introduction to more specialized notations and formal specifications.
Assignment 2b due at 23:59: Final requirements document.
http://se-radio.net/Related to the NY Stock Exchange high-frequency trading issue: Kevin Slavin on How Algorithms Shape our World.
Compose a requirements specification for a given problem domain. It must include functional and non-functional requirements that are properly sectioned and numbered. In addition, 2 types of diagrams or other figures should be used to illustrate the requirements. Your document should be 10—12 pages. You must submit a draft for part 2a and the final version for part 2b. Both versions will be evaluated using a rubric, which is a table describing the expectations over various criteria. Feedback on the draft will be returned in time to incorporate any suggestions into the final deliverable.
The problem domain we will use is “cloud synchronization” — a service like DropBox that will selectively synchronize files and possibly other types of data (contacts, photos) from multiple computers and mobile devices.
©2011 Christopher League · some rights reserved · CC by-sa