Insert Your Name and ClassIT Online Training Application D.docx
- 1. <Insert Your Name and Class> IT Online Training Application Design Specification <Notes: The items in <> are explanatory and should be removed from your final document after you follow the directions. When you submit your specification, make certain that you use the formatting and numbering in this document. This specification highlights some of the design artifacts in an application.> 1. Introduction <Provide a brief introduction of the contents of this document.> 1.1 Purpose <Describe the purpose of this document.> 1.2 Scope <Describe the scope of the software to be produced.> 1.3 References <Insert references to other documents and their sections that are relevant to this document like IT Online Training Analysis Specification and the Analysis Specification.> 2. System Architecture <Provide a brief introduction of the contents of this section and a general description of the software system including its functionality.>
- 2. 2.1. Assumptions and Dependencies <Describe any assumptions or dependencies regarding the software and its use. Consider related software or hardware, operating system, end-user characteristics, etc.> 2.2. General Constraints <Describe any limitations or constraints that have a significant impact on the design of the system’s software and describe its impact. This can include hardware or software environment, end-user environment, availability or volatility of resources, standards, security requirements, memory or other capacity limitations, performance requirements, etc.> 2.3 Proposed System Architecture. <Insert your proposed System Architecture diagram.> 2.3.1 System Architecture Discussion <Provide a discussion of your proposed system architecture and a general description of the software system including its functionality and the specific requirements it meets based on the IT Online Training System Requirements.> 3. 4+1 Architecture <Provide an introduction of the 4+1 architecture. > 3.1 Logical View <According to FCGSS (2007), The logical view “focuses on realizing an application’s functionality in terms of structural
- 3. elements, key abstractions and mechanisms, separation of concerns and distribution of responsibilities.” Include a brief description of the UML diagram you would propose for this view. If you have already created this model, insert it here with a discussion.> 3.2 Process View <According to FCGSS (2007), the logical view “considers non- functional aspects such as performance, scalability and throughput. It addresses the issues of concurrency, distribution and fault tolerance. It shows the main abstractions from the Logical View executing over a thread as an operation.” Include a brief description of the UML diagram you would propose for this view. If you have already created this model, insert it here with a discussion.> 3.3 Implementation or Development View (Subsystem Decomposition) <According to FCGSS (2007), “this is a view of a system’s architecture that encompasses the components used to assemble and release a physical system. This view focuses on configuration management and actual software module organization in the development environment. The software is actually packaged into components that can be developed and tested by the development team”. Include a brief description of the UML diagram you would propose for this view. If you have already created this model, insert it here.> 3.4 Deployment View < According to FCGSS (2007), the deployment or physical
- 4. view” encompasses the nodes that form the system’s hardware topology on which the system executes; it focuses on distribution, communication and provisioning.” This view maps the software to the hardware components. Include a brief description of the UML diagram you would propose for this view. If you have already created this model, insert it and a discussion here.> 3.5 Use Case View <According to FCGSS (2007), the use case view “encompasses the use cases that describe the behavior of the system as seen by its end users and other stakeholders. Include a brief description of the UML diagram you would propose for this view. If you have already created this model, insert it and a discussion here.> 4. Application Class Design <Provide a brief introduction of the contents of this section.> 4.1 Application Class Diagram <An application class diagram includes model (entity), view (boundary), and controller classes that are used to implement a use case. Application classes define the application itself—the software. Insert your application class diagram based on your detailed use case and form/web page mockups.> 4.2 Application Class Diagram Discussion <Discuss your application class diagram based on your detailed use case and mockups.>
- 5. 5. Class Design <Provide a brief introduction of the contents of this section.> 5.1. Detailed Class Diagram <Include your class diagram and the two classes in your Assignment for which you provide a detailed class design including attributes and operations. Add visibility as well. > 5.2. Detailed Class Diagram Discussion <Provide a discussion of your detailed class diagram. Provide a description of the class and discuss the class, attributes, and operations. Use the Use Case and Sequence Diagram or other items to justify the allocation of operations to this class.> 6. Testing <Provide a brief introduction of the contents of this section. You are to create a test case scenario based on your assignment directions and two test cases with discussion for your detailed use case.> 6.1 Test Case Scenario < Provide a test scenario for your detailed use case. Include the test scenario name and description.> Test Scenario Name: <Insert the name of your test scenario here.> Test Scenario Description: <Insert the description of your test scenario here.>
- 6. 6.2 Test Case 1 <Provide a test case based on your scenario above for your detailed use case. Complete the following table for your test case: Test Case 1 Name: Test Case 1 Description: Test Case 1 Prerequisites: Test Case 1 Steps Test Case 1 Input Test Case 1 Expected Result Test Case 1 Actual Result Test Case 1 Status
- 7. > 6.2.1 Test Case 1 Discussion <Provide a discussion of your Test Case 1.> 6.3 Test Case 2 <Provide a test case based on your scenario above for your detailed use case. Complete the following table for your test case: Test Case 2 Name: Test Case 2 Description: Test Case 2 Prerequisites: Test Case 2 Steps Test Case 2 Input Test Case 2 Expected Result Test Case 2 Actual Result Test Case 2 Status
- 8. > 6.3.1 Test Case 2 Discussion <Provide a discussion of your Test Case 2.> 7. Data Design <Provide a brief introduction of the contents of this section.> 7.1 Persistent Data Model <Provide a class diagram (without operations) of persistent data (data that must be stored in some file or database management system). This is usually the domain class diagram (entity classes) with attributes, relationships, and multiplicity constraints specified. You must include primary and foreign keys in your diagram.> 7.1.2 Persistent Data Model Discussion <Include a discussion of the data model.>
- 9. 7.2 SQL Statements <Provide the SQL statements including primary and foreign key constraints for two of your domain classes. Include your class diagram here as well.> 7.2.1 SQL Statement Discussion <Include a discussion of the data model.> 8. Program Implementation <Provide a brief introduction of the contents of this section.> 8.1 Java for Classes <Provide Java statements for your two classes in Section 5 of this document. Follow the examples in Chapter 18 of your textbook.> 8.2 Program Implementation Discussion <Include a discussion of your Java statements. > Appendix. <Insert other material you feed is relevant to the project.> IT Online Training Application Project Part II Page 11 Assignment 5 –Application Classes and Architecture Purpose
- 10. 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
- 11. 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
- 12. 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. Submission Instructions 1. Make certain that your name and course number at the top of the document. 2. When you submit your Word file, use your name as part of the file name, e.g., ENTD321Assignment5_FirstNameLastName
- 13. Your assignment will be graded with the following rubric: Rubric for Assignments Points Content & Development 50% 50/50 Organization 20% 20/20 Format 10% 10/10 Grammar, Punctuation, & Spelling 15% 15/15 Readability & Style 5% 5/5 Timeliness (late deduction 10 points) Optional Total 100/100 Quick Resources Application Class Diagram 1. See Application Class Diagram for an example of an application class diagram and discussion of MVC (Model View Controller). 2. For a discussion of how web pages are integrated into development software see ASP.NET MVC Web-Tier. (2003). Retrieved from http://msdl.cs.mcgill.ca/presentations/030613.Codagen/M VCWebApplication.pdf. This article describes the use of templates for class diagram, web page class diagrams (application class diagram), and navigation activity diagrams for the development of web based applications. 3. Another example of an application class diagram can be found at http://www.cs.gordon.edu/courses/cs211/AddressBookExampl e/Analysis.html.
- 14. Use Case Controllers 1. See the article Use Case Controller that discusses the use of controllers for a Place Order use case. The article takes the Place Order use case discusses it and its activity diagram. Figure 4 on the Place Order realization shows different classes (controllers, interfaces (views), and entity classes) required to implement the use case. Figure 5 shows mockups of the forms for the user interface. Figure 6 shows the relationships between the different types of objects in the MVC pattern. Figure 7 shows a generic model of the pattern. Implementation details follow in the article. 4+1 Architecture 1. Use the following article from your readings to help determine the appropriate UML diagrams to use: FCGSS. (2007). Applying 4+1 View Architecture with UML 2. Retrieved March 20, 2013 from http://www.sparxsystems.com/downloads/whitepapers/FC GSS_US_WP_Applying_4+1_w_UML2.pdf. Covers each of the 4+1 Views with suggestions for using them 2. See the following for a sample architecture for a Course Registration System similar to yours: Software Architecture Document Version 1.0. Retrieved from http://www.ecs.csun.edu/~rlingard/COMP684/Example2SoftArc h.htm#Purpose. Web Architecture 1. Microsoft. (2016). Chapter 21: Designing Web Applications. Retrieved from https://msdn.microsoft.com/en- us/library/ee658099.aspx. This includes a generic web architecture that can be customized for our case study. 2. Generic Web based architecture. Microsoft, (n.d.). Chapter 2: Key Principles of Software Architecture. Retrieved 3/29/2013 from http://msdn.microsoft.com/en-us/library/ee658124.aspx. Software for Architecture Diagrams Our CASE tool does not provide good features for constructing an architecture diagram. You can use draw.io, Word, Visio or other tool.