Software Engineering Methodology Assignment
18 Pages2644 Words195 Views
Added on 2021-01-02
Software Engineering Methodology Assignment
Added on 2021-01-02
ShareRelated Documents
SOFTWAREENGINEERINGMETHODOLOGY
EXECUTIVE SUMMARY1. Specification DocumentThis case study is based on the software engineering methodology. In this Softwarespecification documents are explained with various diagrams and models. In this description ofthe system is given. System description gives a brief description of the system and the hardwarecomponents. It gives a description about how the system programs are linked to each other.Portfolio management system can be used by the portfolio manager, Fund manager, Accountmanager, executive manager and at last by the client. The main function of this system is tomanage and maintain the portfolio of the clients. Scope of the system defines the requirements ofthe systems or the expectations of the system or interface. In simple words it defines what systemwill include or what system will not include, enough details to clearly communicate details to allthe participants or users of the system. This Portfolio management system has all its functionsbifurcated according to the users of the system. Feasibility analysis is the study that is used todetermine viability of an idea like, ensuring the project is technically feasible and legal as well aseconomically justifiable. It also tells whether the project is feasible or not. Requirementspecification describes the requirement of a software system to be developed both functional andnon functional requirements. Assumption and constraints related to the system hare alsodescribed below. Specification description also includes Use case diagrams with its description,Context model and functional modelling.2. Design DocumentIn this case study design document description is also given which includes Architecturaldiagram, hardware specification, class diagram, interface diagram, Business process modelwhich is an activity of representing processes of an enterprise or a system, so that the currentprocess can be improved. In this Allure Investments company does not have a portfoliomanagement system. So here business process model of the PMS system will be made in order tounderstand all the processes of the system. Business process model notation is a simple graphicalrepresentation of specific business processes in a business process model. It uses four types ofobjects such as: events, activities, gateways, connections. These objects further consist of manysub elements. It also consists of sequence diagram, interaction diagram and state diagram.
Table of ContentsEXECUTIVE SUMMARY.............................................................................................................21. Specification Document..........................................................................................................22. Design Document....................................................................................................................21. Specification Document...............................................................................................................4A.) System Description..............................................................................................................4B.) Scope.....................................................................................................................................4C.) Feasibility Analysis...............................................................................................................4D.) Requirement Specification....................................................................................................5I) Functional Requirement......................................................................................................5II) Non-Functional Requirement............................................................................................5E.) Assumptions and constraints.................................................................................................6F.) Use Case................................................................................................................................6I) Diagram..............................................................................................................................7II) Use Case Description........................................................................................................7G.) Context model.......................................................................................................................8H.) Functional Modelling............................................................................................................9Data Flow Diagram.....................................................................................................................9Level 0 DFD.........................................................................................................................102. Design Document.......................................................................................................................10A.) Architectural Design...........................................................................................................10B.) Hardware Specifications.....................................................................................................11C.) Detailed class Diagram.......................................................................................................11D.) Interface Diagram...............................................................................................................14E.) Business process model.......................................................................................................15F.) Sequence Diagram...............................................................................................................16G.) Interaction Diagram............................................................................................................17H.) State Diagram......................................................................................................................18
1. Specification DocumentA.) System DescriptionSystem description gives a brief description of the system and the hardware components.It gives a description about how the system programs are linked to each other (Shehory andSturm, 2016). Portfolio management system can be used by the portfolio manager, Fundmanager, Account manager, executive manager and at last by the client. The main function ofthis system is to manage and maintain the portfolio of the clients. With the help of this system asingle portfolio manager will be able to handle more than 12 clients together. This system willalso help managers to maintain, sell or buy shares for customers and will be able to maintain therecord of customers stock buy or sell activities. This system will require one computer systemwith network connection. Computer will be needing internet connection to run this PMS system.All the calculations related funds will be automatically done by the system. All the users of thesystem will be able to access their profile only and will not be able to access or interfere inothers profile. B.) ScopeScope of the system defines the requirements of the systems or the expectations of thesystem or interface. In simple words it defines what system will include or what system will notinclude, enough details to clearly communicate details to all the participants or users of thesystem. This Portfolio management system has all its functions bifurcated according to the usersof the system. This system requires internet connection to update the market movement of theshares or the funds clients want to sell or buy. It will enable managers to respond quicklyaccording to any movement in the market. This system will also maintain the portfolio of all theclients their funds and dividend. This system will also enable managers to generate tax report.C.) Feasibility AnalysisFeasibility analysis is the study that is used to determine viability of an idea like, ensuringthe project is technically feasible and legal as well as economically justifiable. It also tellswhether the project is feasible or not.Enough technical resources are available in the company for the system to be developed.It helped the technical to develop the portfolio management software.It would be difficult for the technical team to complete the whole project within thelimited cost of the project.
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Database in Software Engineerlg...
|27
|3556
|21
Software Engineering and Methodologylg...
|18
|2871
|52
City Glazier Company Software Requirements Specification Supply Systemlg...
|20
|2776
|481
Specification and Design Document for Sunshine Motorslg...
|22
|2249
|20
System and Design Document for Online Library Management Systemlg...
|21
|2836
|213
Assignment On Airline Reservation Software Requirementlg...
|27
|3396
|4141