System Requirements Specification - Essay Example

System Requirements Specification (SRS) In the current constantly changing technological world, adopting the best software systems has been a very crucial subject of concern in enhancing delivery of high quality healthcare services. The main driving factor in the software development has always been satisfying the targeted user requirements along with being flexible enough to meet the ever-changing global needs for advanced healthcare services (Shelly & Rosenblatt, 2012). Achievement of all these goals by a software team depends hugely on capturing the right requirements for a particular system. On this regard, this paper has laid major emphasis on coming up with a software requirements specification document for the development and procurement of the Product Management System via an account of Pocket Doctor Incorporation. Table of Contents Abstract 2 Table of Contents 3 Introduction 3 Project purpose 4 Project Goals 5 Project scope 5 Project stakeholders 6 Users of the software 7 Functional requirements 8 Non-functional requirements 8 Conclusion 9 Introduction Technological advancement has always been a fundamental aspect in promoting the day-to-day operations of most businesses. This is driven by capturing and putting together a well-organized set of system requirements, which act as the building block to ensuring that, a user satisfying software is developed. On this regard, Pocket Doctor Incorporation (PDI) has always been at the forefront in ascertaining that the best technology is put in place to handle the daily operations of the company. To achieve preciseness in the company’s daily operations, PDI has been gunning for the procurement and development of a product management system. In essence, the main driving factor is to integrate the best technology and promote efficiency and effectiveness in the delivery of healthcare services. In this sense, procurement of product management system has been set aside as the best way forward in meeting the targeted goal of the healthcare centre. Pocket Doctor Incorporation was founded in 2011 with main operational area laid on provision of products for helping patients that suffer from cardiac and respiratory. This is through the use of an advanced Pebble E-paper watch, which monitors and reports the medical condition of a patient. In addition, the watch also delivers onscreen medical advisory services to different conditions that patients undergo. It is hereby vital to note the adoption of a Product Management System (PMS) is aimed at promoting functional efficiency in the company’s current web based retail and monitoring business. The PMS is basically aimed at tracking and monitoring vital signs in customers. In addition, it will play a very crucial role in streamlining the order fulfillment and returns process. In this sense, this SRS document will be a very crucial component in the delivery of a quality PMS for healthcare centre. Project purpose It is essential y to clarify that development and procurement of the proposed product management system is for streamlining the process of monitoring and fulfillment of the orders delivered by the current pocket doctor system. That is, the purpose is to enhance efficiency of the day-to-day operations of the pebble e-paper watch. This is by adequate management of customers’ vital signs through monitoring and tracking. It is also aimed at facilitating smooth management of the order fulfillment process and also returns for rejuvenation of the PDI products (Shelly & Rosenblatt, 2012). Project Goals As stipulated earlier, Pocket Doctor Incorporation is at the forefront in ensuring that it adopts the most recent set of technologies necessary for leveraging its daily business operations. It is because of this fundamental focus that makes the healthcare centre have a considerable of goals for this project (Shelly & Rosenblatt, 2012). Hence, the top goal of the project is to facilitate efficient tracking and monitoring of customer vital signs. Alongside this is integration of software modules that will promote effective management of the process of fulfillment of orders and returns by customers (Shelly & Rosenblatt, 2012) Project scope As aforementioned in the above sections, the main subject of concern in this project is provide an efficient platform and functional area for monitoring and tracking of customer vital signs along with streamlining order fulfillment and returns (Shelly & Rosenblatt, 2012). In order to deliver a project that perfectly fulfills these requirements, the following project scope has been put into close consideration. Firstly, the project should provide a well-defined mechanism that offers functional features where customers can manage their respective accounts. This should include a set of access privileges that limits them to a specified set of tasks that do not interfere with the integrity of the healthcare data. This customer account will directly integrate with the information stored on the respective pebble e-paper watch thus facilitating a streamlined approach towards shipment of products. This project should further provide a module for interfacing a patient’s current condition with the monitoring centre. In addition, to ensure that legal aspects are put into close consideration, the Product Management System will have to be interfaced with the FedEx Shipping System. In terms of report generation, the system will have to provide up to date documentation of all the products that are returned for rejuvenation. Due to technological advancements and the need to promote efficient customer satisfaction and management, the system will have to be developed in a platform that is also usable on a mobile device. Lastly but certainly not the least, the product management system should further provide a bird’s eye view of a well-managed inventory module of the healthcare products (Shelly & Rosenblatt, 2012). Project stakeholders It is very important to outline that there are at least four main groups of stakeholde3rs behind the development of this project. The top group of crucial stakeholder is the company that requires the PMS, which is Pocket Doctor Incorporation. The second one is the solution provider company and its development team, which is Target Solutions Limited. Thirdly, the customers or patients of the healthcare centre are a crucial group of stakeholders since they will be at the forefront of its day-to-day use. In fact, satisfaction of the customer needs will act as the basis to ensuring the healthcare meets its predefined business goals (Shelly & Rosenblatt, 2012). Lastly but certainly not the least, the government and other federal agencies such as those in charge of shipping operations are also important in ensuring that the project delivers the targeted operational objectives (Shelly & Rosenblatt, 2012). Users of the software It is important to outline that there is well-defined set of users of the targeted product management system. In order to ascertain that there system guarantees confidentiality and integrity of the healthcare data, the system has simply laid major emphasis on two main user access levels (Shelly & Rosenblatt, 2012). The top-level users are the PDI employees or representatives and the system administrator. The system administrator will be responsible for ensuring that the PMS go on efficiently. In case of any system challenges or faults, the administrator will also be responsible for handling it. On the other hand the PDI representatives be tasked with logging into the PMS system, add new information about patients and products, documenting products that have been returned for rejuvenation and staying in touch with activities at the monitoring centre. The customer level of users is another crucial group in ensuring that the PMS system ends up promoting the competitive advantage and better service delivery at Pocket Doctor Incorporation. On this regard, a customer, upon being registered on the Pocket Doctor System will be able to conduct online login. This will be through a personal computer and also a mobile device. In addition, the customer will be provided with a number of privileges such as managing his or her account with significant ease. In essence, these access privileges will clearly be a crucial advantage in ensuring that the healthcare centre meets its targeted global competitiveness in delivery of Medicare services (Shelly & Rosenblatt, 2012). Functional requirements It is very crucial to note that for the product management system to be effective, the right set of functional requirements have to be integrated. Hence, this software requirements specification document has outlined the following requirements as the building block to successful achievement of the overall system goal (Shelly & Rosenblatt, 2012). -Login module for PDI employees, system administrator and Customers -A function for users to create an account online -An online access to the PMS software solution for users to download -An integrated function for users to order and activate PDI products -A function to manage and track the status of products under shipment to customers -A well designed database system for storage of company data -An inventory management module for PDI products -A module for interfacing with the monitoring centre -An interface for integration with the FedEx Shipping System -A clearly defined approach towards effective documentation and generation of product reports -Compatibility function for both web based access on both desktop computers and mobile devices Non-functional requirements Usability About this non-functional requirement, the PMS should be provide a direct and ease to remember sequential flow of operations in handling its daily operations. This will make it easy for PDI customers and employees to enjoy its services (Shelly & Rosenblatt, 2012). Compatibility The PMS system will have to be designed with a considerable set of functionalities that will promote efficient operational capabilities on both a personal computer and a mobile device such as Smartphone (Shelly & Rosenblatt, 2012). Interoperability In terms of interoperability, it is crucial to outline that, one of the key operational expectations by the PDI stakeholders is that the PMS will be easily integrated with the FedEx Shipping System. Hence, there is great importance in ensuring that this non-functional feature is satisfied. Reliability The PMS will have to deliver this non functional requirement through ascertaining that all the predefined tasks for each of the users is made available at all times. Performance Performance in the PMS will be delivered by ensuring that each of the predefined functional features in the software works perfectly well at all times. Efficiency For the PMS software solution, the subject of efficiency will be delivered through ascertaining it delivers three crucial features of a quality system. These are confidentiality, integrity and all time availability of the predefined PMS services (Shelly & Rosenblatt, 2012). Conclusion In conclusion, it is important to acknowledge the development of the targeted PMS software solution will largely benefit from this SRS document. The document outlines a well-defined set of functional and non-functional features that act as the building to meeting successful implementation of the project goal. As stipulated earlier, the fulfillment of a quality SRS document for this project is based on a well-defined project scope, which is monitoring and tracking customer vital signs alongside management of order fulfillment and returns of products for rejuvenation. The successful achievement of this quality SRS document is driven by outlining of four main stakeholders. These stakeholders include members of the PDI Company, the software development team, customers and members of the FedEx Shipping System. Hence, this has created the best platform for ensuring that the targeted PMS software solution ends up successful in meeting company goal of being most competitive in the global healthcare industry. References Shelly, G., & Rosenblatt, H. (2012). Systems analysis and design. Boston: Course Technology Cengage Learning. Read More