Customer requires a program to automate his/her media library. This subject area has been selected so you can easily act as your own customer. Include major functions such as:
- the ability to track different types of media (CD, DVD, cassette, Blu-ray, hard cover or paperback books, etc.)
- the ability to differentiate by genre (music, movies, e-books, work or files, etc.)
- the ability to track title, artist (or stars), price paid (for insurance purposes), and other pertinent data about each
- the ability to lend by name, date loaned, expected return date
This not intended to be an exhaustive list of functions nor is the list directive. You can add others you think of or take away functions you don't want to expand. When doing your customer requirements, I would expect you to identify at least three (3) key functions to work with. The purpose of the project is to exercise your use of software engineering concepts to gather requirements and begin the design process.
The project has been selected because you can easily act as both the customer and the developer thereby saving time. You will not be developing code. This is a design project. Although document format is important in the real world, for the purpose of our project I am more interested in seeing that you understand the difference between a high level requirement and a detailed requirement that is both non-ambiguous and testable. Further, I want to see you follow requirements through the detailed design process to ensure the end product satisfies the customer's requirements. With any deliverable, it is more important that you present your material in such a way that other can understand it.
Requirements and Design Deliverables:
1. High level requirements: Since these requirements provide the basis for everything to come, I want to see a lot of thought.
2. Use Cases - Develop use cases for at least four unique activities within one or more of the major high level functions. A use case is a step-by-step sequence for a function that shows user activity and application response (like Loan Media, Add New Media Type, etc.). More information and examples can be found in chapter 11, page 249-252.
3. Detailed requirements. Using guidance provided in the text, (specifically chapters 12 and 13) develop your detailed requirements. Develop as many as possible but you must cover some detailed requirements for each of your high level requirements.
4. Perform detailed design. Identify classes, functions, and algorithms to support your detailed requirements. I realize this is a big assignment, but it is very important to see each step through the process.
5. Unit tests - Using your detailed requirements and design, develop a set of test cases to uncover any defects in the application (see Chapters 25 and 26). For each test case, identify the type of test (boundary value, equivalence partitioning, etc.) and provide the requirement being tested, the input data and the expected outcome. You should be able to identify at least twelve test cases for various detailed requirements.
6. Maintenance - Maintenance can consume as much as 90% of the life cycle costs of an application. Discuss at least three activities associated with maintenance.