ISY302 Software Requirement Specification Assignment Sample

• Subject Code : ISY302
• University : Australian Institute of Higher Education My Assignment Services is not sponsored or endorsed by this college or university.
• Subject Name : IT Computer Science

Project Management Plan

Contents

Project Management Plan (pmp).

Project Management Plan Comprise Following Section:

Executive Abstract..

Project Strategic Alignment..

Project Scope..

Feasibility Assessment..

Project Schedule..

Project Resources.

Risk and Issue Management..

Communication Management..

Approvals.

Attachments.

Real World Project Plan.

Real Time Money Transfer Application.

Er Diagrams.

Description.

Customer Entity.

Acount Details Entity.

Software Requirement Specification (srs).

How to Test Software Requirement Specification and The Key Points While Testing It Well

Accuracy of Software Requirement Specification:.

Equivocation Should Be Avoided:.

Requirements Should Be Completed:.

Unfluctuating Requirement:.

Verification of Expected Result:.

Testing Environment..

Pre-Condition Defined Clearly..

Id Requirement..

Security and Perfomance Criteria..

Assumption Should Be Avoided..

Deletion of Irrelevant Factor..

Freeze Requirements.

Project Management Plan (PMP)

A PMP, or project management plan is referred to as the formal document which defines the way the given project is going to be executed. Mainly it consist scope, goal, budget and the impact of project on the growth of the company. Project management plan is necessary for keeping project on track

• Project management plan must be written during the planning stage of the entire project life cycle and should also be authorized by key stakeholders before it is implemented.
• The main purpose of project is what we want to achieve, how it is to be achieved, what resources we need and how to resolved the risks.
• The PMP is designed as a part of the project initiation and defines the project progress and project all details.

Project Management Plan Comprise Following Section

EXECUTIVE ABSTRACT: This section should include the short summary of whole project including all the key points like high and low points of the project, where to give more attention. Every single key element should be detailed in this section.

PROJECT STRATEGIC ALIGNMENT: This section helps to ascertain the organizational objectives which will be supported by the project execution, and includes the results of the project’s stakeholder analysis.

PROJECT SCOPE: In project scope the objective and the purpose of the project should be written and what will be impact of the project on the company as well as stakeholders. Product or customer service which will be provided by the project to the customer the project scope will be write as the perspective of customer through which you can reached the main demand of the customer and get idea of project scope. All assumption of project must be included in this section. Quality specification should also be a part of this seciton an should describe the project performance criterion.

FEASIBILITY ASSESSMENT: Under this section of the project management plan, the developer evaluates the operational, organizational and technical feasibility of the give project and identify the risk and impact of the project. Blind end of the project has to be evaluated and high end also. Feasibility assessment of the project is very essential in every manner and helps to develop contingency plans which can effectively address risk associated with the project.

PROJECT SCHEDULE: The content of this part of the plan defines the entire project schedule, including duration of the project, last date and critical dependencies. The no. of person involve in this project at what deadline the would submit the project, what will be the circumstances, at what time they have to finish this project as well as which team member is specialized in particular work that work should be allotted to that particular person. 

PROJECT RESOURCES: Under this section, the financial and other resources required to execute the poject are included. Cost estimated or budget may be classified into 3 major part expense, labour and capital. Before all this the cost estimation is must for any project whether it is service provider or product based project. Estimation of total cost is required before the project of the execution. How much money is required for the project, what capital income we have, how much expense will be in the project, is this enough for the project or we can get some loan and many other thing are there in this section.

RISK AND ISSUE MANAGEMENT: In risk and issue management all those things are included which comes from the outside like small issues as well as big issue which cannot be resolve only by manager of the project. So in this we can assume every single blind end of the project through which any type of issue can be create and resolved all this problem before it occur through the full planning and power of assuming like if this happened we will take this step and all.

COMMUNICATION MANAGEMENT: Here, the system of the communication and the performance of the project is described which is provided to the stakeholder of the company as well as the team member of the project.

APPROVALS: This section required or capture the signature or approval of the stakeholder of the project.

ATTACHMENTS- This section should include the business deal paper, notes and some other document of the project.

Real Time Money Transfer Application

For Developing Real-time Money Transfer app first of all we must have a proper Plan for developing application.

We have to calculate total Budget for project, requirement gathering, Risks related to project, Team, maintenance, testing etc.

The life cycle of project will define the strategy for enhancing software quality and the overall process of software development.

After getting all the requirements we have to find best way to reduce risks, budget and manpower.

• We have to hire a developers team like website developers, designers, backend developers, app developers etc..
• We have to create a wireframe of website and apps, so that developers can directly start coding the designs.
• We have to make login system for those employees which are registered or which have bank accounts.
• After entering correct Credentials, user can proceed to login page. and after that we also have to make OTP
• Verification when user will proceed for transfer money to another account.
• We can get OTP from MSG91 or other message sellers.

Description

In ER Diagram we have Entities

• Customer
• Bank
• AccountType
• AccountDetails

• The relationship between Bank and Customer is one to many as a Bank Can have many Customers.
• The relationship between Customer and AccountType is one to many as a Customer Can have many accountType.

Customer Entity

• Customer Entity has attributes such as CustomerID Password, CustomerName, Address, DOB,contactNumber and Gender
• So for doing online transaction user must have a Bank Account.
• After that he can login to the app/website and can enter userID and Password.
• After that user will click on send money button and a form will be open from there , user can choose his account type
• then user have to enter money which we will show through relationship symbol , like if amount entered and < balance amount then user will be not allowed to transfer.

Acount Details Entity

• after that we are at entity Acount Details , if user have entered all the required Attribtes then user will
• get an OTP to registered mobile number.
• if credentials are right then bank will send OTP to users registered phone number. these all functionality will be done through coding.
• after that if OTP is The Last one and entered within 5 minutes then system will approve it and will send userto home
• screen of the App. otherewise it will close the session.

Software Requirement Specification (SRS)

Software Requirement specification (SRS) is a thorough description description of a software system and includes both, non-functional and functional requirments of the system. The software requirement specification is developed on the basis or requirement of customer. It is also an agreement between the customer and company. The software requirement specification includes all the main documents and information of the project. This also include that how the user can interact with the software, how they feel while using it and it is easy to use or not.

• To make any kind of software we have to be in touch with customer to gather their requirement and to meet their expectation.
• A software requirement specification has to be said good when it is properly interrelating with all the inner module, hardware, communicate well with supplementary programs and as well as with human users.
• Using the SRS document on QA lead also help managers to create test plan.
• It is also crucial for testers to clear every detail mentioned in the SRS document to avoid faults in test cases.
• Recommendation to test software requirement specification documents is given by experts before writing test cases making any plan of execution.

How to Test Software Requirement Specification and The Key Points While Testing It Well

ACCURACY OF SOFTWARE REQUIREMENT SPECIFICATION: It is very important to check the accuracy of software requirement specification document because all depend on its accuracy if the SRS is accurate then there will be no problem of correctness of the SRS. There are some standards through which can check and verify the accuracy of SRS.

EQUIVOCATION SHOULD BE AVOIDED: What happened sometimes in SRS there are many meanings of same words which put the testers in trouble of checking it is correct or not. So it is better to use some different type of words or make tester understand better about all the situation of SRS.

REQUIREMENTS SHOULD BE COMPLETED: When the test cases is written by testers, the proper data which is required from the application has to be send to the testers. For example- proper flow chart of the application is required in 500kb. So, this requirement is filled by SRS to the testers.

UNFLUCTUATING REQUIREMENT: The performance of SRS should be consistent in itself and its reference document without any fault because if it is not consistent then we have to face a huge problem related to software. All these things set standard and are supposed to be adhered to throughout the testing phase.

VERIFICATION OF EXPECTED RESULT: There must be not any statement like work as expected by SRS. The work should be proper and verified by testers because every testers have their own individual thinking and the SRS cannot be work on one person thinking .So, the work will be proper and verified by every testers.

TESTING ENVIRONMENT: Some software need specific environment and testing to be accurate in the test because of their favourable conditions for correct result and interaction with other module and hardware. Software requirement specification must have their prominent condition and time to be known well to get correct result.

PRE-CONDITION DEFINED CLEARLY: It is the most important part of getting the correct result by Software requirement specification. Pre-condition of the software will be filled properly in the software through which we cannot get any faults in SRS. It helps us for getting correct result of the SRS.

ID REQUIREMENT: These requirements act as the base of the test case template. Based on requirement of ID’s. Also, it makes it easy to categorized the module by looking at them, tester can ascertain which module to be preferred. SRS define particular if to particular module. 

SECURITY AND PERFOMANCE CRITERIA: If we talking about security and performance then these are two terms which is in the priority list of software developer. Security is very important for any software and its business because every software have very crucial information in it if it is leaked then it can cause harm to the business and as well as the society. So the testers should check all the security requirement needed in software. Second is performance of the software it plays a vital role in the business good performance give good business. The tester test that how much load can take the software under performance some aspects.

ASSUMPTION SHOULD BE AVOIDED: Sometimes the tester should not find all the requirement or test. So tester make some assumption related to the information through which the result may vary and there is no accuracy in result. The tester should avoid these types of assumption and asked the customer to fill the required information through which the tester test SRS well.

DELETION OF IRRELEVANT FACTOR: There are more than one team which worked on SRS. So at the time of testing some irrelevant factors can find by testers they can tell the team or delete all the irrelevant factor from SRS and avoid the work load from the team.

Remember, at the center of any academic work, lies clarity and evidence. Should you need further assistance, do look up to our Computer Science Assignment Help