the assignment is a capstone subject, it only requires one part of the assignment to be done. our project is an e-commerce website and the part to be done for this assignment is external requirements for an e-commerce store/website.
AIH - Project Details ISY3002 2021T2 1 BISY3002 – IS Project 1 IS Project 1 is the first of the two capstone units in your course. So, you are required to work on a real- world project from a client. Your real-world project should contain details of your client’s requirements and your project management plans. This document focuses on the deliverables of the project. In this trimester, the project focus is on the analysis and design of your system. SRS and PMP (Combined) Template link: https://moodle.aih.nsw.edu.au/mod/resource/view.php?id=57829 (Find in the Assessments folder on Moodle if link is not working). Assessment 2 – Systems Definition and Software Requirement Specification (SRS) with Project Management Plan (PMP) report requirements: Please see unit outline for weighting of marks and due dates for this activity. Table of Contents Revision History 1. Introduction 1.1 Purpose 1.2 Project Overview 1.3 Intended Audience and Reading Suggestions 1.4 Project Deliverables 1.5 References 1.6 Definitions and Acronyms 2. Project Organisation 2.1 Process Model: Agile 2.1.1 Project Planning 2.1.2 Requirement Analysis : 2.1.3 Software Design 2.1.4 Analysis Review 2.1.5 Prototype: Front end prototype 2.2 Organisational Structure 2.2.1 Project Manager and Tasks 2.3 Organisational Boundaries and Interfaces 2.3.1 GitHub Communication 2.3.2 Meeting Times 2.4 Project Responsibilities 2 2.4.1 Project Management 2.4.2 Project Sponsor 2.4.3 Liaison Manager 2.4.4 Document Editor 3. Managerial Process 3.1 Management Objectives and Priorities 3.2 Assumptions, Dependencies and Constraints 3.2.1 Assumptions 3.2.2 Dependencies 3.2.3 Constraints 3.3 Risk Management 3.3.1 Analysts Perspective 3.3.2 Design perspective: Front end, process, database 3.3.3 Project Management Perspective 3.4 Monitoring and Controlling Mechanism 4. Technical Process 4.1 Methods, Tools and Techniques 4.2 Software Documentation 4.3 Project Support Functions 4.4 Work Elements, Schedule 5. Overall Description 5.1 Product Perspective 5.2 Product Functions 5.3 User Classes and Characteristics 5.4 Operating Environment 5.5 Design and Implementation Constraints 5.6 User Documentation 5.7 Assumptions and Dependencies 6. External Interface Requirements 6.1 User Interfaces 6.2 Hardware Interfaces 6.3 Software Interfaces 6.4 Communications Interfaces 7. System Features 7.1 System Feature 1 7.2 System Feature 2 (and so on) 3 8. Other Non-functional Requirements 8.1 Performance Requirements 8.2 Safety Requirements 8.3 Security Requirements 8.4 Software Quality Attributes 8.5 Business Rules 9. Other Requirements Appendix A: Glossary Appendix B: Analysis Models Appendix C: To Be Determined List End of Table of Contents Assessment 3 - Software Design Document Please see unit outline for weighting of marks and due dates for this activity. Assessment 3 of this unit requires you to write an SDD. This document should be at a detailed design level. This means, all the major components of the system should be designed with a satisfactory level of granularity such that if your SDD is given to a programmer to implement, it should be easily implementable. In addition, the design should match the requirements specified during the Requirement Analysis activity (see Requirements Analysis section in your A2 document). That is, each design component should be indexed and should be traceable to a requirement specification document. You may use a matrix to manage this. Specifically, designs are required for: business component identification, the front design end, process & workflow design, database design and security concerns in design. You should use the Model View Controller (MVC) framework for the server-side components of the process design. The structure of the SDD should be as follows: Table of Contents 1. Introduction 1.1 Definitions and Acronyms 2. SDD Organization 2.1 Business Component Design: Each Business Component has a specific business purpose should have the following dimensions 2.1.1 Business Purpose: Why does it exist? 2.1.2 Activities: What simple, cohesive activities are regularly performed? 2.1.3 Resources: What tangible assets and human resources are required? 2.1.4 Governance: How are activities and resources managed? 4 2.1.5 Business Services: What is taken form and offered to other components? (consider people, process and technology together) 2.2 Front End Design: Consider structural design of each web page using mock-ups 2.3 Process & Workflow Design: Consider drawing UML activity diagrams for each user story 2.4 Database Design: Provide the overall E-R diagram with explanation and rational 2.5 Security in Design: Consider using STRIDE principles for Application Security 3. Conclusion Please provide the traceability matrix here from requirements to design components. 4. References End of Table of Contents The following five sub-sections discuss these components of the design in more detail. You can add these subsections under Section 2.3 (see Table of Contents provided). 2.3.1 Business Component Diagram A business component diagram identifies the core business components in the architecture. You may draw these as modules and sub-modules required for managing the business. This activity will allow you to think of the business components required for the system without being concerned about the technical aspects of the system. The business component diagram can be drawn using an online diagramming tool such as LucidChart. Link to download: https://lucid.app/pricing/lucidchart (Free). 2.3.2 Front End Design Most modern business applications are web based. Hence the front end-design should be for web- based interfaces. So, you should consider front design from HTML structure perspective but not necessarily using HTML. In other words, you may use mock-up tools such as Mockflow (free), Moqups (trial), Balsamiq (trial) to design the front end. However, in the next semester you should use HTML, CSS, JavaScript and AngularJS during the implementation. CSS or Cascade Style Sheet is a styling language to manage the presentation of the HTML and the data. JavaScript is a browser-based script language for better user interaction and AngularJS is a JavaScript library for separation of concerns such as presentation, data and control on the client side. Watch this video from Edureka for a quick introduction to HTML: https://www.youtube.com/watch?v=UB1O30fR-EE Additionally, you should watch different Youtube/Udemy tutorial videos for a quick introduction to CSS, JavaScript and AngularJS. 5 2.3.3 Process & Workflow Design A process defines a sequence of steps to be completed to accomplish a task and a workflow is a sequence of processes to accomplish a business process. You may consider using the MVC framework in the front-end and in the backend while managing the workflow designs. You are required to use the business components identified in Section 2.3.1 Business Component Diagram as Models within the MVC framework. Read the first five paragraphs from this link to get a quick introduction to MVC. (https://www.tutorialspoint.com/mvc_framework/mvc_framework_introduction.htm). In addition, read the following to learn the principles of MVC framework in front end designs. https://developer.chrome.com/apps/app_frameworks. You should use UML’s Activity Diagrams to draw the workflow design. Your Activity Diagrams should have MVC components wherever possible, both in the front end as well as in the backend. As before you may use LucidChart to draw the diagrams. 2.3.4 Database Design Database designs are required to ensure that the data is structured (organised) appropriately for easy maintenance and efficiency during runtime. You may use MS Access as a tool to design the E-R diagram of the system. This activity ensures that you are knowledgeable of database management principles. 2.3.5 Security in Design Security is a grave concern in most modern web applications. You should design security components in your design. You may consider the Confidentiality Integrity Availability (CIA) principles for this. This (http://www.doc.ic.ac.uk/~ajs300/security/index.html) URL from a student from Imperial College, London provides an easy understanding this principle. Confidentiality can be maintained by using Authentication and Authorization as well as by using encryption. Integrity involves maintaining the consistency, accuracy, and trustworthiness of data over its entire life cycle. Access control matrix needs to be designed to manage this principle. You need to define who can access each resource and whether an actor has “read”, “write”, “execute” privileges to each data management resource used in the system. Availability refers to uptime of the system and how it could be maintained. Templates for PMP & SRS Use one of the following and edit appropriately: https://moodle.aih.nsw.edu.au/mod/resource/view.php?id=57829&redirect=1 http://www.utdallas.edu/~chung/RE/Presentations10F/Team-hope/5%20- %20Project%20Plan.pdf