ITEC 150 - Application Software Assignment
48 Pages10509 Words363 Views
Application Software (ITEC 150)
Added on 2020-03-16
ITEC 150 - Application Software Assignment
Application Software (ITEC 150)
Added on 2020-03-16
ShareRelated Documents
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150Software RequirementsSpecification, SRSForThe Australian Business Company, ABCCRM150“A Customer Relationship Management System”Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage i
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150Table of Contents1.SRS DOCUMENT INTRODUCTION ......................................................................................................11.1PURPOSE OF DOCUMENT ...........................................................................................................................11.2DOCUMENT CONVENTIONS .......................................................................................................................21.3INTENDED AUDIENCE AND READING SUGGESTIONS ..................................................................................22.BUSINESS DOMAIN .................................................................................................................................32.1THE CLIENT ORGANIZATION .....................................................................................................................32.2THE CLIENT ORGANIZATION PROBLEM .....................................................................................................32.3PROPOSED BUSINESS SOLUTION ................................................................................................................33.PROJECT INTRODUCTION ...................................................................................................................53.1PROJECT SCOPE .........................................................................................................................................53.2PROJECT ASSUMPTIONS AND CONSTRAINTS..............................................................................................53.3SYSTEM OPERATING ENVIRONMENT .........................................................................................................63.4PROJECT TESTING APPROACH ...................................................................................................................64.OUR SOFTWARE DEVELOPMENT METHODOLOGY ....................................................................85.SYSTEM FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS......................................... 95.1SYSTEM FUNCTIONAL REQUIREMENTS .....................................................................................................95.2SYSTEM NON-FUNCTIONAL REQUIREMENTS .............................................................................................96.SYSTEM FUNCTIONAL DECOMPOSITION .....................................................................................116.1FIRST SUB-SYSTEM (EXAMPLE, PEOPLE DETAILS MANAGEMENT) ..........................................................146.2SECOND SUB-SYSTEM (EXAMPLE, SALES ORDER PROCESSING) ..............................................................176.3THIRD SUB-SYSTEM (EXAMPLE, REPORTS AND ENQUIRIES) ....................................................................176.4AND SO ON... ....................................................................................ERROR! BOOKMARK NOT DEFINED.7.CANDIDATE SYSTEM CLASS DIAGRAM ........................................................................................268.System Database Modelling and Data Design9.System User Inter FaceAPPENDIX A: GLOSSARY...............................................................................................................................31APPENDIX B: REFERENCES..........................................................................................................................2Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage ii
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150Revision HistoryNameDateReason for ChangesVersionTeam members27 July 2017First Version0.1Hoang Linh Nguyen28 July 2017Add Introduction0.2Shamima Akter and28 July 2017Add Project Introduction0.3ImranMuhammad Umar28 July 2017Add Business Domain0.4HaralAdel Aloqauli28 July 2017Add Software Development Methodology0.5Zheng Wu28 July 2017Add Business Problems0.6Hoang Linh Nguyen28 July 2017General review, combine and edit sections0.7Adel Aloqauli28 July 2017Add use case diagram for the development0.8methodologyHoang Linh Nguyen28 July 2017Add 4.2 Testability (missing due to mistake)0.9and ReferencesHoang Linh Nguyen09/09/2017Improve Introduction1.0Shamima Akter and09/09/2017Improve Project Introduction1.1ImranMuhammad Umar09/09/2017Improve Business Domain1.2HaralAdel Aloqauli09/09/2017Improve Software Development Methodology1.3Zheng Wu09/09/2017Improve Business Problems1.4Hoang Linh Nguyen09/09/2017Add System Functional Decomposition1.5DiagramImran09/09/2017Add first Sub-system (Administration)1.6Adel Aloqauli09/09/2017Add second Sub-system (Sales Order)1.7Zheng Wu09/09/2017Add third Sub-system (Report and Enquiries)1.8Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage iii
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM150Hoang Linh Nguyen09/09/2017Add Fourth Sub-system (Marketing)1.9Hoang Linh Nguyen09/09/2017Update Appendix A and Appendix B2.0Imran09/09/2017Add Candidate System Class Diagram2.1Muhammad Umar27/09/2017Improve Second Sub-system2.2HaralShamima Akter27/09/2017Improve Third Sub-system2.3Zheng Wu27/09/2017Add section 82.4Imran27/09/2017Improve all the use case diagrams and section2.5class diagram (section 7)Shamima Akter28/09/2017Improve Project Scope2.6Hoang Linh Nguyen28/09/2017Add Section 9: User Interface2.7Hoang Linh Nguyen28/09/2017Final review2.8Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage iv
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM1501.SRS Document IntroductionThe introduction of the Software Requirement Specification (SRS) provides an overview of the entire SRS including the purpose of document, document invention, intended audience and readingsuggestions [1]. The aim of this document is to fully define the complete Customer RelationshipManagement 150 (CRM150) system and its functions which were built based on the requirementsrequired by stakeholders and their needs. Nevertheless, this document will present a number of business issues that the client – the Australia Business Company (ABC) is facing caused by the outdated software Sales Manager. The new CRM150 web-based system will be a perfect replacement for the old system and also a powerful tool for the ABC to manage their relationship with customers and to improve the business process.The Unified Modeling Language (UML) will be used for visualizing, specifying, constructing and documenting information about software-intensive system along with a number of use cases to deliver a clear overview of the main system functional and non-functional requirements. The use cases will mainly be used to describe the interactions between users and the system. All of thecollected requirements will also be listed fully in this document.1.1Purpose of DocumentThis Software Requirements Specification document specifically introduce and outline the requirements for the CRM150 web-based system to the ABC senior managers and the executives [1]. One of the main purpose of this document is providing a specific and objective view of the CRM150 system, giving a good explanation of its complete functions. In addition, the mainconcentration will be the requirements required by stakeholders and their needs of changes duringthe testing process. This means that all the requirements made by stakeholders will be documented and analyzed carefully and furthermore, any changing requirement during the testing process will also be responded immediately. All of the requirements made by stakeholders will begathered, analyzed and listed fully in this document.This SRS document contains seven main sections; each section is provided along with its sub-sections.Section 1, SRS Document IntroductionSection 2, Business DomainSection 3, Project IntroductionSection 4, Our Software Development MethodologySection 5, System Functional and Non-Functional Requirements Section 6, System Functional Decomposition Section 7, Candidate System Class DiagramAs a result, this document would be used as the central point of discussion among all the interested stakeholders during the different phases of the system development lifecycle.Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage 1
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM1501.2Document Conventions1.Business term’s first letters are Capitalised.2.Abbreviations are CAPITALISED.3.Important statements are bolded.4.Text in italic needs to be confirmed or replaced.5.The meaning of “must”, “should”, “must not”, “should not”, “may not”, “required”, and “recommended” are defined as in RFC2119.6.Text font used in Times New Roman with the size of 12.7.Text font used for titles is Times New Roman - Heading 1 style (size 18) and subtitles is Times New Roman - Heading 2 style (size14).1.3Intended Audience and Reading SuggestionsThis document is intended for all the system stakeholders, it should be read and reviewed by:1.The senior managers and executives of our client2.The business analysts who are involved in the project3.User and client representatives working in the subject area4.Other reviewers who are experts in the subject areaAlso, this document is to be reviewed and/or used by:1.The project Team as a standard domain vocabulary for communication2.System architect to create Solution Architecture3.System analysts and designers for system design and modelling4.Developers to implement the system1.Testers for software inspections and testing against its principle and agreed-on specifications5.Client and end users for the continual testing and feedbacks6.Documentation writers to create user’s and technical documentsCopyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage 2
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM1502.Business DomainCustomer relationship management refers to the use of practices or strategies that are used by companies for analysing the customer engagements [2]. The main involvement of this process is the analysis of the various sales outlets like websites, stores or emails. CRM helps in analysing the customer interactions and helps in predicting the sales growth. In addition, it also helps in knowing the post engagement required in front of the target audience. 2.1The Client OrganizationThe Australian Business Company, called ABC, is a noteworthy provider of electronic gadgets and a vast supplier of specialized administrations built up in 1980 in Sydney, Australia. The central mission of the organization is showcasing and offering diverse electronic gadgets as a merchant/retailer for some global organizations, for example, Apple, Samsung, IBM, Sony, Groupand Xerox.2.2The Client Organization ProblemAccording the present situation, the company is using an old software application called “Sales Management” which has raised problems due to it outdating that result to current system unable to process insufficiently and functioning satisfactorily. This system could be isolation, non-extensibility, and lacks openness. It will be hard for company to maintain the system due to the expensive cost and the time for understanding internal workings of the system. Moreover, the situation could be serious when the system has tis vulnerabilities that can result to security issues.(1997, B. Wu, D. Lawless, J. Bisbal, J. Grimson, V. Wade, D. O'Sullivan, R. Richardson)2.3Proposed Business SolutionAlthough “Sales Management” unable working satisfactorily, it still can be improved by provide a web-based interface through our service called “Customer Relationship and Business ProcessesManager” that convenient for people who are not familiar with software to use. Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage 3
ITEC150 2017 – Session 2 –– Software Requirements Specification, SRS for Project CRM1503. Project IntroductionThe Australian Business company which is a major supplier of electronic devices and a large provider of technical services established back in 1980 in Sydney, Australia. Currently, the ABC isusing an old computer system. However, according to the present requirements and demands of customer, the old system is no longer suitable. Additionally, in that case of updating this system, it will be very expensive and unrealistic. According to that it has been decided by senior managementof ABC to create a new system. The project will only include the stages of system analysis and design including modelling, database design and user interface.3.1 Project ScopeThe project includes a new software system analysis, design, modelling, database design and user interface design. The need for new business requirements is mainly due to ABC's problem as the existing system is no longer functioning adequately due to its age and insufficient and unsatisfactory capabilities. In addition, the project includes an high-level description of a potential solution to help the fundraising organisation to achieve their major objectives3.1.1 Project Inclusive Aspects (Within the Project Scope)The main aspects included in this project are the statement of the organization problem, business drivers and technical constraints, functional Requirements, use case and system class diagrams, non-functional Requirements, database design and model [3].3.1.2 Project Exclusive Aspects (Out of the Project Scope)The following aspects are out of the project scope:1.Programming and coding2.Unit testing3.System environment setup4.System hosting and deployment facilities5.System configuration6.System backup and restore facility7.End users training8.System maintenance and upgrade3.2 Project Assumptions and ConstraintsThe main assumptions include licensing and general requirements for the business to use CRMsuccessfully. In addition, a remote sever set up which will provide sufficient security protection as user’s personal information will be stored in the database. Moreover, staff will need to be adequately trained in advance to easily transition from the old system increasing efficiency.Furthermore, budget will be provided and managed by the client and storage of files will be facilitated to fit government legislations of 6 years.The various assumptions and constraints that needs adherence are included here. The software must be accessible via a cloud based facility providing security and 24/7 access. In addition, transactions and records must be stored to adhere to government legislations for a minimum of 6 years.The software must have compatibility features to enable user access from various platforms and operating systems [3]. In addition, security of payments and information, like credit cards, PayPal or bank transfer must be facilitated. Moreover, scalability to the client’s requirements and Service Oriented Architecture Approach must be implemented.Copyright © 2017 by group 1 - Modification and/or distribution of this document is not permitted without permissionPage 4
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Online Magazine Management System Software Specification Documentlg...
|24
|3546
|69
Software Engineering: SRS Document, Process Model, Use Cases, and Morelg...
|35
|8787
|395
Software Requirements Specification for Online Book Shoppinglg...
|35
|9476
|325
System Analysis and Designlg...
|18
|2607
|110
Annotated Template for the Software Requirements Specification Assignment of WSU-TC CptS 322lg...
|23
|3430
|202
Software Engineering Methodology Assignmentlg...
|18
|2644
|195