17-10-2016, 11:33 AM
1459349617-CSMS.doc (Size: 1.92 MB / Downloads: 5)
INTRODUCTION
Aim:
Intended Audience and Reading Suggestions and Document Overview
In recent years, several forces have been driving an evolution of student information systems and, as a result, leading many institutions to replace theirs. Those forces are:
• Demand for 24/7 web-based access to information by students, instructors, and parents
Present Working System :
• Existing system maintenance College Sports Data in paper records. It is not secure manner.
• This existing system is not providing secure registration and profile management of all the student, counselors properly.
• Having all information in the form of paper records it is not in secure and time taken process to get data immediately.
• Data searching process is not there. It is not user friendly.
• No facility to add new courses, new branches.
• No facility to add games data like game type, game name, and games related rules files.
• No facility to student applies games.
• No facility to view student apply games.
• No facility to view student applied games.
• No facility to add games participant’s data.
• No facility to view games participant’s data.
• No facility to add result card data.
• No facility to view result card data.
To Be Praposed :
• The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach.
• Easy maintenance all the data related to sports, games, participants, result card records.
• This system maintains Student’s addresses and contact details.
• It provides facility to add new courses, new branches.
• It provides facility to add games data like game type, game name, and games related rules files.
• It provides facility to student applies games.
• It provides facility to view student apply games.
• It provides facility to view student applied games.
• It provides facility to add games participant’s data.
• It provides facility to view games participant’s data.
• It provides facility to add result card data.
• It provides facility to view result card data.
• User friendliness is provided in the application with various controls provided by system rich user interface.
• Authentication is provided for this application only registered Students, coach, admin can access.
FEASIBILITY REPORT
FEASIBILITY REPORT
TECHNICAL FEASIBILITY:
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical
analysis.
i) Understand the different technologies involved in the proposed system:
Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system.
ii) Find out whether the organization currently possesses the required technologies:
o Is the required technology available with the organization?
o If so is the capacity sufficient?
For instance –
“Will the current printer be able to handle the new reports and forms required for the new system?”
OPERATIONAL FEASIBILITY:
Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project:
Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.
Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more operational and useful systems.
Have the user been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in
General and increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.
ECONOMIC FEASIBILITY:
Economic feasibility attempts 2 weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.
A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.
Operating Environment :
SOFTWARE REQUIREMENTS
Operating System : Windows XP/2003 or Linux
User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java , Servlets, jsp
IDE/Workbench : My Eclipse 8.6
Database : Oracle 10g
Server Deployment : Tomcat 6.x
HARDWARE REQUIREMENTS(Minimum requirements)
Processor : core 2 duo
Hard Disk : 160GB
RAM : 1GB or more
Design and Implementation Constraints :
The system is designed using the Spiral model, with constant interaction with the clients. The implementations design is done thru java Servlets and jsp with HTML, CSS, and JAVASCRIPT.
The software will be required to be maintained by the TOMCAT 6.0. The website administrator is sole responsible for the maintenance of the site all Users authentication restricted. Sufficient security through firewalls and proxy to be implemented.
It also requires the Oracle 10g database to store and retrieve data.
Project Planning:
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.
The steps for Spiral Model can be generalized as follows:
• The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
• A preliminary design is created for the new system.
• A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
• A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning an designing the second prototype.
4. Constructing and testing the second prototype.
• At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
• The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
• The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
• The final system is constructed, based on the refined prototype.
• The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.
ADVANTAGES
• Estimates(i.e. budget, schedule etc .) become more relistic as work progresses, because important issues discoved earlier.
• It is more able to cope with the changes that are software development generally entails.
• Software engineers can get their hands in and start woring on the core of a project earlier.
1. THE PRESENTATION LAYER
Also called as the client layer comprises of components that are dedicated to presenting the data to the user. For example: Windows/Web Forms and buttons, edit boxes, Text boxes, labels, grids, etc.
2. THE BUSINESS RULES LAYER
This layer encapsulates the Business rules or the business logic of the encapsulations. To have a separate layer for business logic is of a great advantage. This is because any changes in Business Rules can be easily handled in this layer. As long as the interface between the layers remains the same, any changes to the functionality/processing logic in this layer can be made without impacting the others. A lot of client-server apps failed to implement successfully as changing the business logic was a painful process
3. THE DATA ACCESS LAYER
This layer comprises of components that help in accessing the Database. If used in the right way, this layer provides a level of abstraction for the database structures. Simply put changes made to the database, tables, etc do not affect the rest of the application because of the Data Access layer. The different application layers send the data requests to this layer and receive the response from this layer.
4. THE DATABASE LAYER
This layer comprises of the Database Components such as DB Files, Tables, Views, etc. The Actual database could be created using SQL Server, Oracle, Flat files, etc.
In an n-tier application, the entire application can be implemented in such a way that it is independent of the actual Database. For instance, you could change the Database Location with minimal changes to Data Access Layer. The rest of the Application should remain unaffected.
External Interface Requirements
3.1 User Interfaces
The application to be provided with keyboard shortcuts and a facility to use the mouse to trigger the required actions. They act as shortcuts and provide an easy navigation within the software. Error detection is handled by using Exception handling. Exception class is used to trap abnormal conditions and terminations.
3.2 Hardware Interfaces
The system requires an Internet connection with a decent band width. A printer in addition to take printouts of reports. A internet connection that is either thru dial-up, cable , modem, Wi-Fi is required. Appropriate networking and protocols should be.
3.3 Software Interfaces
The incoming data to the product would be raw text data and outgoing data would be text itself. Both input and output are handled thru dynamic HTML. A browser is required for access.
Users of the System :
1. Administrator
2. Coach
3. Student
Modules of the System
1. Administrator
2. Coach
3. Student
4. Search
5. Security & Registration
6. Home