C++ Question

Background

For this deliverable, your team is expected to furnish the following components. All items must be diligently addressed unless prior arrangements have been mutually agreed upon. The work submitted must meet the standards of completeness, accuracy, persuasiveness, and professional presentation. Any deviations from these expectations should be communicated in advance for appropriate consideration. This ensures that the deliverable not only adheres to specified requirements but also reflects a high level of professionalism and competence.

Instructions

Design Concepts: (Section 3.2 & 3.3)

Software design is the crucial process of creating a comprehensive engineering representation or model for a planned software product. Designers face the challenge of building a diverse repertoire of alternative design information and selecting elements that align most effectively with the analysis model. This involves thoughtful consideration of various factors to ensure the resulting design model is a fitting response to the customer’s requirements.

Key Points:

1. Quality Assessment of Design Model:

1. 1. The design model, stemming from the customer’s requirements, undergoes a rigorous assessment against predefined criteria to ensure quality.
   2. The evaluation process aims to identify and rectify errors, inconsistencies, or omissions. It also considers the existence of better alternatives and assesses whether the design model aligns with project constraints.

1. 1. Each design product undergoes a thorough quality review before progressing to the subsequent phase of software development.
   2. The review process ensures that the design model is not only error-free but also aligns optimally with the project’s goals and constraints.

Create a set of Use Case (show actors, processes, system boundaries) and Data Flow Diagrams (DFD) for the system you are proposing. Be sure to include essential administrative functions in your diagram. Write a brief narrative for each Data Flow Diagram explaining the data flow. Indicate the entitys priority level (A, B, C – explained below), all preconditions, post-conditions, and triggers for the entities. Briefly describe all actors (users, systems, or organizations) who interact with your system, as indicated in your diagram. Do not assume that the meaning of any entity, actor, or function is obvious to your readers; your descriptions must be very clear and unambiguous.

Note: Each entity must be assigned a priority:

A – Essential for system operation.

B – Not essential for system operation but would add significant value to system’s users or stakeholders.

C – Would add some small, but real or perceived value to the system’s users or stakeholders.

Upload your Deliverable (One submission per team) in the digital dropbox. Make sure of the following before you upload the files.

1. Use your name and Deliverable number as File Name. (e.g. Last Name of all team members_Deliverable_1).
2. Add your name and assignment number at the top of first page for example: // Last Name of all team members Deliverable #1.
3. Make sure you send the file in DOC. or DOCX format only.
4. Handwritten/drawn and scanned files are not acceptable and will not be graded.
5. Only electronic submissions via digital dropbox are acceptable.