Please see attached filesUnit Name/Code ISY3002/ISY302 IS Project 1 Assessment Number 2 Assessment...

Question

Please see attached filesUnit Name/Code ISY3002/ISY302 IS Project 1 Assessment Number 2  Assessment Name Project Management Plan (PMP) & Software Requirement Specification (SRS)  Report – Group Assesment  2. Demonstrate an understanding Graduate Attributes Assessed Communications of the roles and responsibilities of Unit Learning Outcomes Critical thinking & problem solving software developers, clients and Ethical behaviour Assessed users of a system. Flexibility  3.Conduct a feasibility study that Communications  outlines costs, timeframes, a Collaborations  development schedule, and the Research  features and benefits of a Critical thinking & problem solving  Ethical behaviour prospective software solution. Flexibility  4. Demonstrate skills in project Communications  planning and management, Collaborations  problem solving, analysis, and Research  evaluation. Critical thinking & problem solving  Ethical behaviour  Flexibility  Due Date and Time  Weighting  Week 7, 15 January 2021 by 5 PM AEST  40%  Assessment Description A 4000-word or equivalent effort report on PMP and SRS based on your  client’s project details. Refer to the document titled “AIH - Project Details  ISY3002 2020T3.pdf” for the project specifications. This report should be in  MS Word format. SRS documents typically contain several types of UML/other  diagrams and tables. If you are using other tools to generate the diagrams  paste the generated images on to the Word document.  Note that the report is not an essay and should not be text heavy.  Detailed Submission Upload the document via Moodle/Turnitin.  Requirements Follow the instructions as required by this assessment brief.  ISY302 - IS PROJECT 1, T3 2020 A2 ASSESSMENT BRIEF  1 | P a g e  I NSTRUCTIONS  This is an individual activity. You will participate in weekly tutorial/workshop activities to complete most of the contents required in  the report.   NATURE OF THE TASK This is an individual assessment.  MATERIALS REQUIRED / SUGGESTED RESOURCES   Refer to the document titled “AIH - Project Details ISY3002 2020T3.pdf” for your project specifications. You will need to use many  tools to create the report. The tools required could be GitHub, Balsamiq, UML diagramming editors such as LucidChart or Visio.  HOW TO PRESENT YOUR ASSIGNMENT / SUBMISSION INSTRUCTIONS   Your report should follow the structure specified in Section 2.3.1 in “AIH - Project Details ISY3002 2020T3.pdf”. You will submit  the work via Moodle/Turnitin.   RETENTION OF RECORDS  Students are required to keep a copy of all items submitted or completed for assessment or evaluation until the end of the  grade appeal period.  I NFORMATION ABOUT HOW AND WHEN FEEDBACK WILL BE PROVIDED  Your results of the assessment will be available within 1 week of the submission of the report. Feedback will be in the  form of comments on the document along with the marks awarded following the marking criteria.  MARKING CRITERIA  See the rubric in the next page. ISY302 - IS PROJECT 1, T3 2020 A2 ASSESSMENT BRIEF2 | P a g e  ASSESSMENT RUBRIC - TASK BASED  Section Requirements Total Highly Fairly Competent Competent  Needs improvement Work needs review  Competent  Overview:  1. Introduction to the topic CompletesALL Completely fulfils Partially fulfils Completes any Has not completed 2. Introduction to the structure of the document FIVE criteria FOUR out of FIVE THREE any THREE out of 10% CORRECTLY criteria CORRECTLY ALL FIVE criteria    out of FIVE criteria FIVE requirements 3. Introduction to the deliverables   4. Follows structure specified in the introduction 5. Grammar & logical flow 10 8 6 4 0  Requirements Engineering  CompletesALL Completely fulfils Completes any Has not completed 1. Identification of various actors Partially fulfils  FIVE criteria FOUR out of FIVE THREE any THREE out of 2. Identification of external entities, boundaries and CORRECTLY criteria CORRECTLY ALL FIVE criteria out of FIVE criteria FIVE requirements interfaces 20%  3. Identification of core business requirements 20 16 12 8 0 4. Identification of security requirements 5. Front end prototypes for requirements gathering  Project Management  CompletesALL Completely fulfils Partially/ Has not completed  1. Assumptions, dependencies & concerns Inaccurately Completes any two three criteria TWO out of THREE any two out of three  2. Risk management plan fulfils ALL three out of three criteria 10% CORRECTLY criteria CORRECTLY criteria 3. Monitoring & Control mechanisms criteria  10 8 6 4  0  /40 Overall comments:TOTAL MARK  ISY302 - IS PROJECT 1, T3 2020 A2 ASSESSMENT BRIEF   3 | P a g e     Microsoft Word - srs_template.doc Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document. Software Requirements  Specification  for    Version 1.0 approved  Prepared by       Software Requirements Specification for   Page ii Table of Contents  Table of Contents .......................................................................................................................... ii  Revision History ............................................................................................................................ ii  1. Introduction..............................................................................................................................1  1.1 Purpose ............................................................................................................................................ 1  1.2 Document Conventions.................................................................................................................... 1  1.3 Intended Audience and Reading Suggestions.................................................................................. 1  1.4 Project Scope ................................................................................................................................... 1  1.5 References........................................................................................................................................ 1  2. Overall Description.............................................................................

Neha · Accepted Answer

Microsoft Word - srs_template.doc
Software Requirements
Specification
for

Version 1.0 approved
Prepared by 


Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Table of Contents
Table of Contents	ii
Revision History	ii
Introduction	1
Purpose	1
Document Conventions	1
Intended Audience and Reading Suggestions	1
Project Scope	1
References	1
Overall Description	2
Product Perspective	2
Product Features	2
User Classes and Characteristics	2
Operating Environment	2
Design and Implementation Constraints	2
User Documentation	2
Assumptions and Dependencies	3
System Features	3
System Feature 1	3
System Feature 2 (and so on)	4
External Interface Requirements	4
User Interfaces	4
Hardware Interfaces	4
Software Interfaces	4
Communications Interfaces	4
Other Nonfunctional Requirements	5
Performance Requirements	5
Safety Requirements	5
Security Requirements	5
Software Quality Attributes	5
Other Requirements	5
Appendix A: Glossary	5
Appendix B: Analysis Models	6
Appendix C: Issues List	6
Revision History
	Name
	Date
	Reason For Changes
	Version
	
	
	
	
	
	
	
	
 (
Software Requirements Specification for 
) (
Page ii
)
1. Introduction
The software requirement specification is generally designed in the form of a document which help us to describe the agreement which is created between the developer and the customer with respect to the specification about the software product which is requested by the customer. The primary aim of the software requirement specification document is to provide a descriptive and clear statement about the user requirements which can be further used by the developer as the reference to develop the software system. The whole document is broken into multiple sections which can be He used separately in the logical manner for the software requirements with the help of the referenced parts. The major aim of the software requirement specification is to describe about the external interfaces, design constraints, attributes and the functionalities which can be used for the implementation of the software system which is described in rest of the document in detail. This document contains the description about the software system, the technology and the language which will be used, and it remains consistent throughout the whole document. This document is based on the requirement specification for the books ecommerce system. 
1.1 Purpose
The major goal of the software requirement specification document is to describe and define the specifications and all the functions which will be included in the book ecommerce system. This software requirement specification can be used to illustrate the primary usage and required functionality of the system in the clear and easy terms as per the specification shared by the customer. The intended audience for this document is the primary customer of the book ecommerce system. This whole document tries to cover the detailed information and the requirement of implementing the book ecommerce system. This document contains all the requirements, non-functional requirements, interfaces and diagrams which can be used for the implementation of the software system. 
1.2 Document Conventions
The whole document of the software requirement specification is subdivided into multiple sections. The first section is used to explain about the scope, purpose and the organization of the whole specification document. In the first section we will try to handle this description about the project in few specific words, abbreviations and acronyms which will be used in the document. The second section present in the document is all about the product. It is subdivided into 5 different sections and each of them will be used to provide detail about the specific system like its uses and the corresponding actions. In this section we will discuss about the product functions, assumptions and the dependencies, product perspective, user characteristics and the product functions. The 3rd section will be used to discuss about the requirements which will be present in the system. In this section we will try to enumerate the whole list about the requirements which can describe the book ecommerce system in detail. In the 4th section we will try to understand the interfaces which are very important for the whole system. The report also consists of few appendices which shows the diagrams, Glossary of the whole document and the importance and the issues which can be faced while implementing the ecommerce book system. 
1.3 Intended Audience and Reading Suggestions
This requirement specification document is generally for those audience which are interested in implementing the book ecommerce system and needs to use it. This document can be used by the audience to understand how the system will actually work and how it can be implemented. It describes all the requirements which will be required for implementing the system by the development team. For understanding the whole document, it is important for the audience to have the basic knowledge about the English language and few basic terms about the development of any system. The audience should start with the first section of the document and then it should go to the appendix A and then appendix by which will help them to understand the document and the system with the help of diagrams. Later the audience can come to the section 2 and so on to further understand the system in terms of the functional and non-functional requirements and the different interfaces. 
1.4 Project Scope
The software which will be implemented with the help of this software requirement specification is known as the book ecommerce system. This product is being produced as per the interest of the customer for selling the books over the Internet. The whole system will be designed so that it can provide automation support to the customer during the process of placing the books for the sale over the Internet and providing the facility for the actual cell. This system can be used as the cross platform and it will be Available for all the users who are using the computer resources. This system is will be able to run over the central server with each user who are having the remote user interface with the help of the web browser for having interaction with the system. The book ecommerce system is designed in such a manner that it will allow the user to create an account over the system and become a regular customer for it. The customer needs to understand the whole process of account creation and he will be able to create the account and become the member of the whole site. The system will also allow the customer to search for the books, select the book or add any book to the shopping cart. Once the customer has added few or single book in their shopping card then the system will allow them to check out books present in the shopping cart and reduce the stock which is present in the inventory which is maintained by the system in backend. The book ecommerce system will also allow the manager to have access to the inventory for managing the book stock. The manager will be allowed to create, update, delete or retrieve the information with the reference of the books present in the system. The system will also allow the manager and customer to interact with each other for the promotion which can handle the percentage for the promotions, and they can be applied to the orders of the members.

Unit Name/Code ISY3002/ISY302 IS Project 1 Assessment Number 2 Assessment Name Project Management Plan (PMP) & Software Requirement Specification (SRS) Report – Group Assesment 2. Demonstrate an...

Answer To: Unit Name/Code ISY3002/ISY302 IS Project 1 Assessment Number 2 Assessment Name Project Management...

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment