Software Requirement System Assignment Sample

Software Requirement System  Assignment Sample

1. Introduction

The following document details out the basic software requirement to be developed and also talks about the project scope. In addition to this, all the functional and non-functional requirement of the PMIS that are quintessential for the software development.

• Purpose

The following SRS document lists out the specific requirement of the proposed project management information system (PMIS) for the BGC Construction and its project management operations. The performance metrics and action plan for the same system are elaborated here.

2. Brief about the Proposed PMIS System- ‘Teamwork’

The ‘Teamwork’ PMIS is comprising two subsystems that are specifically designed for proper sequencing among various processes associated with the BGC Constructions. Once implemented, it would bring transparency, discard complexities, and increase the process completion rate (Wickboldt, et.al 2015). It is characterised by journey mapping and the ability to integrate with other software, such as MS Office and Google Drive.

You Share your Assignment Ideas

We write it for you

• Most Affordable Assignment Service
• Any subject, any Format, Any Deadline

Order Now whatsapp Order

2.1.Business Process

The business processes associated with BGC Construction are

• Planning
• Sales
• Design
• Estimating
• Scheduling
• Materials management
• Contracting
• Cost control
• Quality management
• Safety management
• Human resource management
• Accounting/financing
• General administration
• R&D

3. Requirements for Teamwork PMIS

3.1.Functional Requirements

Functional requirements are capabilities that are required to satisfy the specific needs of the users. These can be termed as business requirements and are the capabilities that are expected from the proposed PMIS- ‘Teamwork’

• FR1

ID	FR1
Title	Multi-platform Compatibility You Share your Assignment Ideas We write it for you Most Affordable Assignment Service Any subject, any Format, Any Deadline Order Now whatsapp Order
Description	The PMIS should be available not only for Windows Users but also for iOS
Rational	For all type of users
Dependencies

3.1.2. FR2

3.1.3. FR3

3.1.4. FR4

3.1.5. FR5

3.1.6. FR6

3.2.Non-Functional Requirements

There are some non-functional requirements also associated with the ‘Teamwork’ system. These are related to its security, performance, and audit (Wickboldt, et.al 2015). These are further elaborated below:-

Security

The organisation is aiming at providing a unique identity and credential to every employee from the lowest to the highest level. The primary concern of the company is the security. The system should aim at protecting data and private information of any employee. The users are required to change the initial password after the first login. In addition to this, the system would send a reminder after every 60 days to change the password. In addition to this, in case the login is done from an unknown device, then a message is sent to the user about the unauthenticated login. In addition to this, the security issues also comprise concerns for intellectual property rights, security frameworks, data privacy software, restricted technology export, etc. Hence, they should be audited regularly (Afolabi, et.al, 2017).

Performance

The PMIS should be designed portable in order to move from one OS to other OS. In addition to this, it should provide the user with the required information he/she seeks as agreed on the Service Level Agreement (SLA). The performance requirement is already mentioned in the agreement and all the requirements are clearly mentioned by the organisation. The platform should be able to handle enough traffic at the same time.

Audit: The history of every change done in the system should be saved and available whenever required. In addition to this, all the failed attempts made by the staff shall be recorded.

Reliability:The system is developed while considering all the international standards. It can be able to handle the large traffic and search request at the same time. In addition to this, the system is connected with reliable servers and is developed with a 99% uptime SLA guarantee.

Constraints: Nobody is allowed to update any financial data except the executives. Hence, the tracking devices are necessary for the systems. The system application is designed for desktops only. Mobile or any other device use is restricted to date in order to avoid security threats. One can only access to the new information through the PMIS only when the computer device has an active internet connection.

Hardware Requirement:

• Minimum 4GB RAM
• GPS systems in the Laptop for location tracking
• Wi-Fi connection is needed for updates
• Internet Connectivity

4. Business Continuity Plan

This would ensure recovery and prevention from potential threats to BGC construction. The proposed PMIS used by the company can help in building up an effective Business Continuity Plan (Schwalbe, 2015).

• Business Impact Analysis:  The PMIS would be comprising the information regarding time-sensitive functions and related resources.
• Recovery:  The management of BGC Construction would be able to identify and implement measures to recover acute business operations using the information (Gao, et.al, 2014).
• Organization: Once this is done, a continuity team would be formed. It will help in developing a plan to cope with the disruption.
• Training: The continuity team should be provided some training for handling such threats and emergencies.

5. Performance Metrics

• Productivity: PMIS should be able to calculate the amount of input and output in a process in order to evaluate productivity (Joseph, et.al, 2015).
• Gross Profit Margin: The ultimate motive of implementing the PMIS is to improve the gross profit of the company.
• Return on Investment: the benefits of PMIS may comprise the contribution, cost saving, improvement in process, increased output.
• Employee Satisfaction Score: PMIS should also be able to collect the employees’ related data and feedback in order to evaluate employee satisfaction index.
• Cost Performance: It is called cost-efficiency metric. PMIS should be able to forecast cost effectively.
• Schedule Variance: PMIS should be able to evaluate the time taken by each and every project activity.

6. Acquisition Proposal of IS System

Since BGC construction lacks the required skills and ability to develop the PMIS of its own, the company is going for external acquisition (Thakurta, 2013). The acquisition process is comprising the following steps:-

• Identification of system requirements, selection & planning.
• Analysis of various systems
• Developing a Request for Proposal (RFP)
• Proposal Evaluation
• Vendor Selection

It is recommended that the SDLC (System Development Life Cycle)approach would be used in developing the system (Andreassen, et.al, 2015 ). The following SDLC would be aiming at the security of data and privacy of employees and organisation. Once the SDLC gets terminated, the acquisition of IS initiates. It comprises the following steps:-

• Determine Software Requirement
• Incorporate Software Functional and Non-Functional Requirements into Specifications
• Obtain the system related activities, such as evaluation and monitoring the systems
• The system is tested and installed.

7. Recommendations

The effectiveness of the system is tested based on KPIs and system performance:-

• BGC construction aims at improving the productivity of the employees and organisational processes. If PMIS is implemented properly, then this would help in improving the productivity.
• PMIS should be able to reduce the operational cost by reducing the number of defects & faults.
• PMIS should be able to improve the quality of the processes and their outcomes. The quality should be one of the KPIs (Thakurta, 2013).
• Timely deliveries is another success factor for the PMIS as the project has some deadlines and they should be met on time.

8. Project Workflow

The project workflow for the development of this ‘Teamwork’ is shown in the figure provided below. The existing model will be giving priority to repeated testing and simulations (Gottschalk, et.al, 2008). This would reduce any kind of discrepancies related to the programme.

9. Conclusion

The complete development of the proposed PMIS for BGC Construction would be done based on the aforementioned functional and non-functional requirements. In addition to this, the proposed workflow plan would ensure that the proposed system is free from all sort of issues and technical glitches.  

10. References

• Afolabi, A., Fagbenle, O., &Mosaku, T. (2017). IT Management of Building Materials’ Planning and Control processes Using Web-Based Technologies. In  World Conference on Information Systems and Technologies(pp. 12-19). Springer, Cham.
• Andreassen, H. K., Kjekshus, L. E., &Tjora, A. (2015). Survival of the project: a case study of ICT innovation in health care.  Social Science & Medicine,  132, 62-69.
• Gao, S., Xu, H., Jia, Y., Mobasher, A., Bayesteh, A., &Cai, Z. (2014).  U.S. Patent No. 8,644,422. Washington, DC: U.S. Patent and Trademark Office.
• Gottschalk, F., Van Der Aalst, W. M., Jansen-Vullers, M. H., & La Rosa, M. (2008). Configurable workflow models.  International Journal of Cooperative Information Systems,  17(02), 177-221.
• Joseph, N., Erasmus, W., &Marnewick, C. (2014). The idle state of information and communication technology project management.  Journal of African Business,  15(3), 184-196.
• Schwalbe, K. (2015).  Information technology project management. Cengage Learning.
• Taghavi, M., Patel, A., &Taghavi, H. (2011, September). Web base project management system for the development of ICT project outsourced by the Iranian government. In 2011 IEEE Conference on Open Systems  (pp. 267-272). IEEE.
• Thakurta, R. (2013). A value-based approach to prioritise non-functional requirements during software project development. International Journal of Business Information Systems, 12(4), 363-382.
• Wickboldt, J. A., De Jesus, W. P., Isolani, P. H., Both, C. B., Rochol, J., & Granville, L. Z. (2015). Software-defined networking: management requirements and challenges. IEEE Communications Magazine, 53(1), 278-285.