Introduction
The Brooklyn Shop is needs a requirement specification document for their e-commerce website. The document will covers all aspect which will solve the problems identified. The document will focus on the key issues and should also comply with the international standards of developing e-commerce system. The requirement specification will particularly focus on functional, non-functional and other system requirements that are relevant to Brooklyn Shop business.
The document gives a detailed description of functional and non-functional requirement for Brooklyn Shop’s integrated web-based system’s which will be implemented in a forth night. This document is to act as a basis of collecting requirement process used in eliciting the requirements from the stakeholders. The document also gives a brief definition of the goals and vision of the system, and to outline the functional and non functional requirements that are critical to the system’s success.
This document is created with in-depth understanding that having in place proper business objective and vision in an information technology product and a well developed documentation which is robust, complete and consistent functional and non functional requirement is critical for a system success.
References
IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE Std. 1471-2000.
IEEE Recommended Practice for Software Requirements Specifications, IEEE Std. 830-1998.
IEEE Guide for Developing System Requirements Specifications, IEEE Std. 1233-1998.
Requirement process
System requirement elicitation process in a software engineering process which gives a stand and documents with the software system functional and non functional requirements as formulated via contrastive collaboration and interaction between different stakeholders and the development team.
User Requirements Overview
The company is looking for ways to leverage the management of hiring, but wants to ensure that the information technology infrastructure will support the expected growth that the company is anticipating (Jue 85). The system should gather the company’s scalability since this is a relatively new system; there is currently limited technology infrastructure to support the business. All information technology components such as hardware and software should be redesigned to meet organizational needs. The most appropriate method solve the problem face by the company is a hybrid model.
This project is to automate the operation of their business by implementing an enterprise information system that will incorporate all the business process and handle the key business processes including financial transaction such as salaries, personal information administrative activities and employee monitoring.
The IT roles of the project is the ability of the system to provide integrated functionality that is able to combine the key components of data collection, analysis, financial and the entire administration process with a lot of efficiency, reliability accuracy and effectiveness, and at the same time ensure the security of the company’s information. This will in turn increase the company’s profit (Vallet 855).
In general, though the current system has been working without any limitation, the expansion of the business will bring about a large number of problems that need to be addressed by implementing a new system that in addition to solving the named problem, Brooklyn shop will be able to have reports that will analyze data for accurate decision making and at the same time provides a basis of evaluating the trends in the business and hence provide a basis being ahead of the competing firms.
System Requirements Specification
Functional requirements
- The system should enable the Brooklyn Shop to manage all its employees in a central point by use of a centralized database system that will store all the information concerning the employees.
- The system should have a module or a package that will manage product cataloging. The module enables the user to feed all the information when applications are made.
- The system should have a module for managing all the financial transaction in the company (Maiden 52).
- The system should have a page for procurement management. This can be achieved by integrating a SAGE accounting software. This software should have adequate security to manage online payment
- The system should have a module for shipping information management purposes. It should ensure that all the shipping data is stored in a centralized repository so that the time taken to process shipping is reduced.
- The system should also be able to deduct all the reduction that a particular customer owes the shop. It should also cross-check the customer’s credit card balances so that fraudulent activities are eliminated.
- The system should also have a package for tracking the performance of every employee.
Non functional requirement
- The system has short response time
- The user interface should be simple
- Complete navigation between different sub-system
- Usability should be simple
- Enhanced efficiency
Constraints
The following constraints have been identified:
• The current information technology infrastructure is not strong enough to fully support the new system. Some of the key components that limited are server storage space. The processor speed of the server, the system’s ability to accommodate future also needs to be improved. The internet connection also is very slow.
• Time frame- the company allocated extremely short time to the project. This implies that the resources and cost will be affected.
• Human resource that is required to implement the system.
• We have the issue of staff sabotage where a number of staff is not ready to accommodate the changes that are brought to the company (Jonasson 98). Therefore they try to bring down the system by for example giving the wrong input.
Implementation Phases
Implementation team should consider data warehousing best practices which will aid immensely in requirements gathering effort
Applications: the applications which are given priority include database, data warehousing components that will enable the company to meet the short term IT strategies. The hardware and other support software are also given priority.
Process Re-engineering: Re-engineering will involve integration of cloud computing features and components to the system to ensure that all long term company’s business needs and IT requirements are met.
Customization: Customizations will be limited to the analytic features. This is to come up with a subsystem that will provide users with flexible and straightforward system
Interfaces: The interfaces included are features that ensure that the users in each and every business unit view the right interface (Corporation 56). This will include both functional and usability interface components.
Architecture: Application and Technical Architecture should be designed according to the system’s requirement specifications.
Testing: The testing should be carried in two stages. First every system unit is thoroughly tested. This is done by exposing the prototype system to the users. The errors that will be realized are fixed before system integration. Another test will be performed after the different sub systems are integrated.
Funding: The project funding covers only the activities that are specified in the project scope. These include the purchase of software, hardware, network components, expenses on the project team and training
Training: Training will be conducted in phases. All the employees in different business units should fully understand the system and how it works. The security issues should also be dealt with during the training.
Future Directions and Expected Changes
The developers should also get in touch with employees in the various departments to provide some guideline of the sub-system that will be more effect effective in handling the business operations in the department. This includes recommending the vendor that can provide state of the art Customer Relationship Management software.
BPMN DIAGRAM
The above BPMN diagram above shows how the customer views the product of the shop’s website and makes an order. The customer first goes to the shops website and view the product. There website homepage display different categories of product. Once the customer has decided on the product, he can start the purchasing process by login into the system. New customers are providing the option of singing up to become a regular customer or can proceed without creating an account. The customer specifies the product that he or she is interested in buying then give the shipping and payment detailed. The system will first check the payment information to ensure that the customer’s credit card has enough balance. Once the payment details are confirmed, the system will respond to by sending a confirmation mail to the customer to acknowledge that the order has been received. The message also gives the client a tentative shipping period.
Website Design prototype
Work Cited
Brennan, Hashi. Getting it right: Business requirement analysis tools and techniques. Cengage learning, 2010.
Corporation, Tracor. System Requirements Analysis. Geneva, 2009.
Jonasson, Heyson. Determining project requirements, second edition: Mastering the babok and the cbap exam. CRC Press, 2011.
Jose, Stewar. Systems analysis and design in a changing world. Indiana University, 2011.
Jue, G. M., Shumaker, S.N. and Evans, G. W. "Benefit System Requirements: Checklist for Reviewing Systems Unde." Journal of system analysis 4: 337-345.
Kryter, K.D. "Systems analysis and design." Journal of the System analysis 17 (n.d.): 1222-1242.
Maiden, Neil. Information technology: Project management. Wiley India Pvt. Limited, 2011.
Meecham-William, C,. system requirement & development life cycle. Los Angeles: University of California, 2005.
Vallet. Systems analysis and design. 5th. sweden: Sweden Council, 2009.
