12-09-2013, 03:46 PM
AUTOMATED BUSINESS INTELLIGENCE NETWORK FOR SOFTWARE REQUIREMENT SPECIFICATIONS
AUTOMATED BUSINESS.doc (Size: 434.5 KB / Downloads: 14)
INTRODUCTION:
This project Automated Business Intelligence Network is a web-based project. This project mainly deals with automating the tasks of maintaining and transacting the goods. In the Business Intelligence Network, inventory management is the key process. This process includes the activities such as maintenance of stock details, maintenance of receipts and items etc. It is a tedious job to maintain all these details manually. Hence we opted to automate the Business Intelligence Network.
PURPOSE OF SRS:
The purpose of this Software Requirement Specification (SRS) is to help the project. It is provided with some requirements which are used in BIN. All parts; design, coding and testing will be prepared with helping of SRS. The purpose of this document is to detail the requirements placed on the BIN and serves as a contract between the customer and the developers as to what is to be expected of the Smart card, and how the components of the system are to work with each other with external systems..
SCOPE:
As the scope of business intelligence expands, every decision-maker can benefit from predictive modeling applications. Embedding predictive models within Web FOCUS applications extends their usefulness tremendously. We’ve accomplished this with Web FOCUS Restart, a statistical modeling workbench that allows data miners and BI developers to work collaboratively to access, manipulate, and transform data.
PROGRAMMING LANGUAGES:
JAVA: Java technology is a high-level programming and a platform independent language. Java is designed to work in the distributed environment on the Internet.
HTML, XML: Hyper Text Markup Language and Extensible markup Language are the predominant markup languages for web pages. It provides a means to describe the structure of text-based information in a document and to supplement that text with interactive forms, embedded images, and other objects.
JavaScript: A client side scripting language used to create dynamic web content and user interface.
FUNCTIONAL REQUIREMENTS:
Following is a list of functionalities of the system.
BIN splits your screen up into various sections. At the home page there are list of menu options. These allow you to go straight to a category you want by navigating through the sub options.
Admin can view and modify card info by logging on to their account.
Admin add all the suppliers details.
Admin add the required stock for retailers.
Admin add the Sub location Interchanges for adding the suppliers.
Supplier adds retailers details.
Supplier handles all the orders for providing services for retailers.
NON-FUNCTIONAL REQUIREMENTS:
The system should be web-based system. Users should use the system via internet. Each user should have a user account. The system should ask the username and password to users. It doesn’t permit to unregistered user to access for BIN. The system should have Role based System functions access. Approval Process has to be defined. The system should have Modular customization components so that they can be reused across the implementation.
SDLC METHODOLOGIES:
This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
N-TIER ARCHITECTURE:
Can easily implement the concepts of Distributed Application Design and Architecture. The N-Tier Architecture provides strategic benefits to Enterprise Solutions. While 2-tier, client-server can help us create quick and easy solutions and may be used for Rapid Prototyping, they can easily become a maintenance and security night mare.
The N-tier Applications provide specific advantages that are vital to the business continuity of the enterprise. Typical features of a real life n-tier may include the following:
Security
Availability and Scalability
Manageability
Easy Maintenance
Data Abstraction
The above mentioned points are some of the key design goals of a successful n-tier application that intends to provide a good Business Solution.
DEFINITION:
Simply stated, an n-tier application helps us distribute the overall functionality into various tiers or layers:
Presentation Layer
Business Rules Layer
Data Access Layer
Database/Data Store
Each layer can be developed independently of the other provided that it adheres to the standards and communicates with the other layers as per the specifications.
This is the one of the biggest advantages of the n-tier application. Each layer can potentially treat the other layer as a ‘Block-Box’.
In other words, each layer does not care how other layer processes the data as long as it sends the right data in a correct format.