The purpose of this assignment is to begin the design modeling for our ITOT Case Study. For this assignment, you will develop an application class diagram that includes entity, view, and controller classes as well as an architecture diagram.
In this assignment we will begin the design for the case study, the IT Online Training Project. You have already completed sample analysis specifications for this case study. This assignment is based on the IT Online Training Project Requirements 2018R2. In this assignment you will develop an application class diagram and the software architecture for the application. The software architecture is usually developed at the very beginning of analysis and design, is continually updated, and is the guiding document for the design of the application.
You will use the new Design Specification Template 2018 document to create your design specifications. Make certain that you keep the formatting and numbering of the template for your assignments. The Design Specification Template is a Word file with predefined sections that you will complete each week as you did with the Analysis Specification. In this assignment you will create an application class diagram for your detailed use case and you will also create a system architecture for your application.
In this assignment you will complete the following sections of your Design Specification:
1, 1.1, 1.2, 1.3 Introduction to the Project
2, 2.1, 2.2, 2.3, 2.3 System Architecture Diagram for Case Study
3, 3, 3.1, 3.2, 3.3, 3.4, 3.5 4+1 Architecture
4, 4.1, 4.2 Application Class Diagram
Instructions
1. Review the IT Online Training Project Requirements 2018R2 and your previous submission for the project.
2. Review the Quick Resources listed at the end of this assignment and the resources for Week 4..
3. Open the Design Specification Template 2018 and save it as ENTD321Assignment5_FirstNameLastName.
4. Sections 1, 1.1, 1.2, and 1.3. Complete Sections 1, 1.1, 1.2, and 1.3 of the Design Specification. These are just introductory comments. You can use the Analysis and Requirements Specification documents as references.
Application Class Diagram
5. Sections 4, 4.1, 4.2. Develop an application class diagram that includes entity classes (domain classes), view (boundary) classes like screens and forms, and controller classes that mediate between the view classes and model classes.
5.1 Use your detailed use case (Manage Shopping Cart) as the basis as well as your sequence diagram. Review other use cases to make certain that the application class diagram supports the use case functions. Usually we start with one controller for each use case and name it using the name of the use case and the word “Controller”.
5.2 So for application class diagram start with a controller named after your detailed use case. Use your CASE tool to create the application class diagram. Add text that includes your name and course number directly on the diagram.
5.3 Add view classes for the forms you identified for your detailed use case in your analysis specification.
5.4 Use your sequence diagram for your detailed use case and add the objects as classed to your application class diagram.
5.5 Include a discussion of your application class model and how it works.
5.6 Insert your application class diagram into Section 4.1 of your design specification. Complete Sections 4 and 4.2 (discussion) of your design specification.
System Architecture Diagram
6. Sections 2, 2.1, 2.2, .2.3. Develop a System Architecture diagram for your IT Online Training application and include a discussion of the 4+1 architecture. Use some of the Microsoft suggested techniques or the web application techniques and present your architecture. I suggest that you might want to look at the Microsoft generic MVC architecture discussed in Lesson 5 and the Web Architecture article at the end of this assignment.
6.1 Use your CASE or other tool and create an architecture diagram for the IT Online Training application. Insert it into Section 2.3 of your design specification. Complete Sections 2 (introduction to contents of section), 2.1 (assumptions and dependencies), 2.2 (general constraints), and 2.3.1 (discussion) of your specification.
7. Sections 3, 3.1, 3.2, .3.3, 3.4, and 3.5. Complete Sections 3, 3.1, 3.2, .3.3, 3.4, and 3.5 with an analysis of the 4+1 Architecture. See FCGSS (2007) in the Quick Resources . Each section has instructions for completing it. Essentially you will include the following:
3.1 Logical View –a brief description of the UML diagram you would propose and if you have already created the model, insert your model into the section.
3.2 Process View–include a brief description of the UML model you would propose for this view and if you have already created the model, insert your model into the section.
3.3 Implementation or Development View–a brief description of the UML diagram you would propose and if you have already created the model, insert your model into the section.
3.4 Deployment View–include a brief description of the UML model you would propose for this view and if you have already created the model, insert your model into the section.
3.5 Use Case View–include a brief description of the UML model you would propose for this view and if you have already created the model, insert your model into the section.
