School Management System allows users to store almost all of their school’s information electronically, including information on students, properties, teaching meteorites etc. Most importantly, this information can be easily shared with authorized users, records can be easily searched, and reports can be easily generated. The project objectives are: -Suggestion of a management system that will provide a solution to some problems in high school for course planning and evaluation of teachers in a given time, and meet the system requirements. Designing a new system that will provide a good way and easy to manage the delivery of courses – Ensure system security. 1. 3 Problem Definition: SMS has most of the facilities that a modern school requires to computerize its day-to-day jobs. It provides facilities to keep the records of student, fees, teaching and non-teaching staff with all their required details along with all required transaction handling. It has facilities to generate various types of reports, which are required by the management during normal business operations to operate the business effectively.
School Management System is software which is helpful for students as well as the school authorities. In the current system all the activities are done manually. It is very time consuming. 1. 4 Problem Description: This project is basically a Student information system with some new extra features like Student Registration,Student’s,Marksheet,Student Result and many other features, the common functions of a student records system are to support the maintenance of personal and study information relating to: * Handling inquiries from prospective students * Handling the admissions process Enrolling new students and storing teaching option choices * Automatically creating class & teacher schedules * Handling records of examinations, assessments, marks, grades and academic progression * Maintaining records of absences and attendance * Recording communications with students * Maintaining discipline records * Providing statistical reports * Communicating student details to parents through a parent portal Need and Scope: To manage the students details and all to develop power. The main scope of the SAMS is to ensure the systematic efficiency in school administration and the delivery of service mechanism.
The Essay on School Record Management System
... their information. Background of the Study Students ought to be more cognizant identified with their school records/ documents ... manner as whatever other business stake, recorded data requires compelling administration. Records administration guarantees data might be ... student records when they transferred to other schools. The system will not cover other Student records except from ECC The system ...
This is Java Projects on School Management System, which provided a lot of facility to their user. The objective and scope of my Project School Management System is to record the details various activities of user. It will simplifies the task and reduse the paper work. During implementation every user will be given appropriate training to suit their specific needs. Specific support will also be provided at key points within the academic calendar. Training will be provided on a timely basis, and you will be trained as the new is School Management System rolled out to your area of responsibility.
At the moment we are in the very early stages, so it is difficult to put a specific time on the training, but we will keep people informed as plans are developed. The system is very user friendly and it is anticipated that functions of the system will be easily accessed by administrators, academics, students and applicants. Hence the management system for the College management has been designed to remove all the deficiency from which the present system is suffering and to ensure. Functional Requirements The functional requirements of the system are: • register a student, record attendance of students, • generate various reports, • generate timetable. 2. Analysis Model : To produce a model of the system which is correct, complete and consistent we need to construct the analysis model which focuses on structuring and formalizing the requirements of the system. Analysis model contains three models: functional, object and dynamic models. The functional model can be described by use case diagrams. Class diagrams describe the object model. Dynamic model can also be described in terms of sequence, state chart and activity diagrams.
The Essay on Modeling And Simulation System Model Data
As simulation is increasingly applied to more complex applications, exploiting efficiencies in model design and model execution becomes a challenging task. Thus the creation of modeling charts, tools, and diagrams... 18 March 2003 A system is understood to be an entity which maintains its existence through the interaction of its parts. A model is a simplified representation of the real system ...
For the purpose of this project we have described the analysis model in terms of the functional model and dynamic models using use case and sequence diagrams. 2. 1 system design In the previous chapter we have identified the functional and non-functional requirements of the system and produced the analysis model. The following are discussed in this chapter: design goals, system architecture, system decomposition, deployment and database design. 2. 2 Design Goals Design goals describe the qualities of the system that developers should optimize. Such goals are normally derived from the non-functional requirements of the system.
Design goals are grouped into five categories. These are • Performance • Dependability • Maintenance • End User Criteria 3. Performance Criteria The part of the system to be used for the record office should have a fast response time (real time) with maximum throughput. Furthermore, the system should not be taking up too much space in memory. The record officer has chosen fast response time over throughput and hence the system should try to be more interactive. In the case of the timetabling subsystem, the system should be more reliable in order to satisfy the constraints than fast response time. . 1 Scope: This project is aimed at how the institute can improve the efficiency of the services. School Mangement Systems is one of the application to improve the information of any particular student. This application involves almost all the features of the information system to retrieve the data of any particular student. The future implementation will be online help for the users to obtain information. 4. Document Conventions: This project is a menu driven program. When we click the main menu the sub menus or different forms will be enabled. 4 . 1 Definitions, Acronyms, Abbreviations:
The Term Paper on Web Server System User Interface
Project 5: Good Neighbors Campaign Project Description: Develop a database to keep track of 20 data points for each of USC's 10, 000 employees for the past 10 years (and years to come). This database would need to have the ability to generate reports based on various queries in order to answer questions about donation trends among the University employees. Team Members: David Stark David Jena ...
The program consists of the following modules. * Masters This module is suppose to hold the details of any particular students, courses, subjects. * Attendance This module is suppose to hold the total number of classes held and the total number of classes attended by any student. * Examinations This module is suppose to hold the examination details or the marks scored by the students in the examination held. * Reports * This module gives the whole details of the students attendance report and students marks report. 5. Overall Description: it describes all general factors of the product and its requirements. 5. Product perspective: School Mangement Systems is independent and dynamic applicaion. This application stores all the information in the database which can be retrieved whenever needed and all the validations are performed during the entry of the data by the user thus ensuring that the user can not enter any wrong data which could cause problem later. 5. 2 Product Features: This section outlines all the main feature of School Mangement Systems. 5. 2. 1 Student role: In the project Student updates all detail such as Address and contact number. The system will generate password to the students. 5. 2. 2 Administration Role:
The system administrator must be able to: * deactivate and reactivate student account login * force the sending of a new password to a student via email change any of a student’s details. 6. User Class and Characteristics: The user of this program is supposed to be fairly educated about the usage of the computers. The user should understand how to get the data through the system. A person who has no knowledge of computer will find it difficult to understand the system. But with a little knowledge it will be very easy to handle the project. 7. Design and Implementation Constraints: 7. 1 Software Constraints: JDK6. 0 * MS ACCESS 7. 2 Hardware Constraints: * 80 GB hard disk and above * 1 GB RAM * Dual Core 8. Assumptions and dependencies: Although basic password authentication and role based security mechanisms will be used to protect from unauthorised access; Redundant Database is setup as the role of backup Database Server when primary database is failure. 9. External Interface Requirements: 9. 1 User Interface: * User class – Student Change Detail: Student can change detail if information is incorrect such as telephone number. Change Password: Student can change his login password at any time for security reason.
The Term Paper on Group Member System Student Information
System Development ITC 712 Project Proposal Prepared for: Mr. Samsudin Md. Strip Prepared by: Lizawati Bakri (2003215593) Mohd. Farhan Md.Fudzee (2003661166) Shadil Akimi b. Zainal Abidin (2003215952) Masters of Science in Information Technology (MSc. IT) CS 770 Project Title: "STARIS" Sekolah Tuanku Abdul Rahman Information System Due date: 1 August 2003 TABLE OF CONTENTS 1) Introduction To The ...
Forget password: Student can request his password if he/she forgotten the password. * User class –Staff All staff can view the details of any student. Change Student Detail: Staff can change student detail for incorrect information. View Student Detail: Staff can view student information and monitor their progress. List Student : Staff can list all students in different semester of different group. Change Password : Staff can reset the student’s password if required. * User class – System Administrator List Student: System Administrator can list all students in different period of different group to check any error.
Change Password : System Administrator can reset the student’s password if required. * User class – Administration Staff List Student : Administration Staff can list all students in different semester of different group. 10. System Features: 10. 1 System Feature 1: Student Information System will allow the user to view the attendance, marks details of the students. This is a medium priority system feature. 10. 2 Module 1:Masters This module is suppose to hold the details of any particular students, courses, subjects. Input: The user is supposed to make selection of the list given. Output: The admin gets the details of the student. 0. 3. Module 2:Attendance This module is suppose to hold the total number of classes held and the total number of classes attended by any student. Input: The user is supposed to make selection of the sub modules and choose the options. Output: The attendance details of the students will be shown. 10. 4 Module 3:Examinations This module is suppose to hold the examination details or the marks scored by the students in the examination held. Input: The user should make the selection of examination. Output: The marks details of the student will be shown to the user. 10. 5 Module 4:Reports
This module gives the whole details of the students attendance report and the of the students marks report. Input: The admin can only choose the reports generation process. Output: The updated file will be displayed. Limitation: The School Management System eliminates most of the limitations of the existing software. It has the following objectives: * Enhancement: The main objective of School Management System is to enhance and upgrade the existing system by increasing its efficiency and effectiveness. The software improves the working methods by replacing the existing manual system with the computer-based system. Automation: The School Management System automates each and every activity of the manual system and increases its throughput. Thus the response time of the system is very less and it works very fast. * Accuracy: The School Management System provides the uses a quick response with very accurate information regarding the users etc. Any details or system in an accurate manner, as and when required. * User-Friendly: The software School Management System has a very user-friendly interface. Thus the users will feel very easy to work on it. The software provides accuracy along with a pleasant interface.
The Research paper on Age Verification Systems and Closed User Groups in Germany
Federal Department for Media Harmful to Young Persons The Voluntary Self-Regulation of Television Interstate Treaty on Broadcasting and Telemedia Protection of Young Persons Act -Jugendschutzgesetz Telecommunications Act Commission for the Protection of Minors in the Media Age Verification System Closed User Group 3 Introduction Media accessibility via internet is rapidly increasing within the ...
Make the present manual system more interactive, speedy and user friendly. * Availability: The transaction reports of the system can be retried as and when required. Thus, there is no delay in the availability of any information, whatever needed, can be captured very quickly and easily. * Maintance Cost: Reduce the cost of maintenance. Other Non Functional Requirements: 11 . 1 Performance Requirements: The system is supposed to be having good memory space and a bigger RAM above 700MB preferably. The system shall be able to add more details. 11. 2 Safety Requirements: The system will do periodic backups of database. 11. Security Requirements: The system shall encrypt all students data in the database. 11. 4 Software Quality Attributes: 11. 4. 1 Security: The system needs to log client’s information of registration such as computer name and time for security purpose. Password should encrypted and store in the database. 11. 4. 2 Maintainability: The system developing using Java Swing controls with jdk6. 0 and all record stores in MS Access Database, that easy to modify and make update. 11. 4. 3 Portability: The web application is coding in JAVA and MS Access, therefore, it should be transferable between different Operation System.
1. 4. 4 Testability: The system must be able to run under debug mode. 11. 4. 5 Reusability: The coding can be used whenever needed throughout the development of the project instead of writing the code again and again. 12. Structure: This is useful for: * Administration/principal * Student/Parents * Teachers Main Features: * view/take attendance * Reaport Cards Section * Exam Schedule * Student profile * School bus details 13. Data Flow Diagram: A Data Flow Diagram (DFD) is a graphical representation of the “flow” of data through an Information System. A data flow diagram an also be used for the visualization of Data Processing. It is common practice for a designer to draw a context-level DFD first which shows the interaction between the system and outside entities. This context-level DFD is then “exploded” to show more detail of the system being modeled. ER Diagram:Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases. An Entity Relationship Diagram is a piece of data-an object or concept about which data is stored. RESEARCH METHODOLOGY 3. 1 Introduction The third chapter states the methodology used to reach the objectives of the project.
The Research paper on A comparative analysis of traditional software engineering and agile software development
... data resources while UML uses modelled stereotype features as data sources. Question 4 Software development approach entails identification the information system issues and making decision ... as Individual and interaction over processes and tools, Working software under comprehensive documentation, Customer or end user collaboration over a contract negotiation ...
The framework in which software is designed, developed, and maintained is known as the Software Development Life Cycle (SDLC).
It shows the steps, phases, milestones, and evolution of the software development process. There are many types of models used in software design and development. Among them are the spiral models, rapid development model, Evolutionary model, waterfall model, prototyping model, etc. 3. 2 Prototyping model Prototyping Model has been used to develop this application. The Prototyping model is a technique for quickly building a function but incomplete model of the information system. . 3 Advantages of prototyping · Reduces development time. · Reduces development costs. · Requires user involvement. · Developers receive quantifiable user feedback. · Facilitate system implementation since users know what to expect. · Results in higher user satisfaction. · Exposes developers to potential future system enhancements. 3. 4 Disadvantages of prototyping · Can lead to insufficient analysis. · Developers can become too attached to their prototypes. · Can cause systems to be left unfinished and/or implemented before they are ready. 1 Whitten Bentley, «Systems analysis and design methods 7th edition», p. 70 3. 5 The process of prototyping > Identify basic requirement: Determine basic requirements including the input and output information desired. Details, such us security, can typically be ignored. > Develop initial prototype: The initial prototype is developed that includes only user interfaces. > Review: The customers, end-users, examine the prototype and provide feedback on additions or changes. > Revise and enhancing the prototype: Using the feedback, both the specifications and the prototype can be improved.
This method involves a series of iterations and refinement until the prototype product is a fully working system, and the user is satisfied. 3. 6 The importance of using prototyping It has been argued that prototyping, in some form or another, should be used all the time and is very effective in the analysis and design of on-line systems, especially for transaction processing, where the use of screen dialogs is much more in evidence. However, prototyping is most beneficial in systems that will have many interactions with the users. Prototyping is especially good for designing good human-computer interfaces. . 7 Analysis of the system The initial step while developing an application program consists exactly to find out what to be solved and what should be done and to make sure that the measures taken are consistent and sufficient to resolve the problem. It also consists of finding out what are the requirements specifications that the system will use, who are the users, what is the benefit of the application, those activities are done to help full system analysis 3. 7. 1 The existing system There is no any other automated product at Kigali International School.
The current system is manual. They use Ms Excel, which is so difficult to use, where the user must memorize all features of the tool and this is not easy and results to different errors. 3. 7. 2 The proposed system While analyzing the existing system, the automated system has been proposed. This is the School Management System. It allows the user to store data, retrieve data and manage simply. Secretary can insert teachers’ information, course information, distribute courses among available teachers, inform all teachers for changes and other related to school activities 3. . 3 System requirements Ubuntu Linux Operating system revealed itself as a product of choice because of viruses’ issue, but that product can also run under Windows XP, Vista as Operating System, Processor 2. 5 GHz and 1014 MB RAM and 60 GB Hard Disk for each machine. 3. 8 System Actors System actor is any person who will use or affected by an information system on a regular basis-capturing, validating, entering, responding to, storing and exchanging data and information. The School Management System has two categories of the system users.
They are: · School Secretary. · System Administrator. The Software Development Life Cycle (SDLC ) As in any other engineering discipline, software engineering also has some structured models for software development. This document will provide you with a generic overview about different software development methodologies adopted by contemporary software firms. Read on to know more about the Software Development Life Cycle (SDLC) in detail. Curtain Raiser Like any other set of engineering products, software products are also oriented towards the customer.
It is either market driven or it drives the market. Customer Satisfaction and Customer Delight were buzzwords many decades ago. Customer Co-creation is the new buzzword that’s been doing the rounds. Products that are not customer or user friendly have no place in the market although they are engineered using the best technology. The experience of the product and the participation of the customer in creating the product is as crucial as the internal technology of the product. Market Research A market study is made to identify a potential customer’s need.
This process is also known as market research. Here, the already existing need and the possible and potential needs that are available in a segment of the society are studied carefully. The market study is done based on a lot of assumptions. Assumptions are the crucial factors in the development or inception of a product’s development. Unrealistic assumptions can cause a nosedive in the entire venture. Though assumptions are abstract, there should be a move to develop tangible assumptions to come up with a successful product. Research and Development
Once the Market Research is carried out, the customer’s need is given to the Research & Development division (R&D) to conceptualize a cost-effective system that could potentially solve the customer’s needs in a manner that is better than the one adopted by the competitors at present. Once the conceptual system is developed and tested in a hypothetical environment, the development team takes control of it. The development team adopts one of the software development methodologies that is given below, develops the proposed system, and gives it to the customer.
The Sales & Marketing division starts selling the software to the available customers and simultaneously works to develop a niche segment that could potentially buy the software. In addition, the division also passes the feedback from the customers to the developers and the R&D division to make possible value additions to the product. While developing a software, the company outsources the non-core activities to other companies who specialize in those activities. This accelerates the software development process largely.
Some companies work on tie-ups to bring out a highly matured product in a short period. Popular Software Development Models The following are some basic popular models that are adopted by many software development firms A. System Development Life Cycle (SDLC) Model B. Prototyping Model C. Rapid Application Development Model D. Component Assembly Model A. System Development Life Cycle (SDLC) Model This is also known as Classic Life Cycle Model (or) Linear Sequential Model (or) Waterfall Method. This model has the following activities. 1. System/Information Engineering and Modeling
As software is always of a large system (or business), work begins by establishing the requirements for all system elements and then allocating some subset of these requirements to software. This system view is essential when the software must interface with other elements such as hardware, people and other resources. System is the basic and very critical requirement for the existence of software in any entity. So if the system is not in place, the system should be engineered and put in place. In some cases, to extract the maximum output, the system should be re-engineered and spruced up.
Once the ideal system is engineered or tuned, the development team studies the software requirement for the system. 2. Software Requirement Analysis This process is also known as feasibility study. In this phase, the development team visits the customer and studies their system. They investigate the need for possible software automation in the given system. By the end of the feasibility study, the team furnishes a document that holds the different specific recommendations for the candidate system. It also includes the personnel assignments, costs, project schedule, target dates etc….
The requirement gathering process is intensified and focussed specially on software. To understand the nature of the program(s) to be built, the system engineer or “Analyst” must understand the information domain for the software, as well as required function, behavior, performance and interfacing. The essential purpose of this phase is to find the need and to define the problem that needs to be solved. 3. System Analysis and Design In this phase, the software development process, the software’s overall structure and its nuances are defined.
In terms of the client/server technology, the number of tiers needed for the package architecture, the database design, the data structure design etc… are all defined in this phase. A software development model is thus created. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase. 4. Code Generation The design must be translated into a machine-readable form.
The code generation step performs this task. If the design is performed in a detailed manner, code generation can be accomplished without much complication. Programming tools like compilers, interpreters, debuggers etc… are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen. 5. Testing Once the code is generated, the software program testing begins. Different testing methodologies are available to unravel the bugs that were committed during the previous phases.
Different testing tools and methodologies are already available. Some companies build their own testing tools that are tailor made for their own development operations. 6. Maintenance The software will definitely undergo change once it is delivered to the customer. There can be many reasons for this change to occur. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period. B. Prototyping Model
This is a cyclic version of the linear model. In this model, once the requirement analysis is done and the design for a prototype is made, the development process gets started. Once the prototype is created, it is given to the customer for evaluation. The customer tests the package and gives his/her feed back to the developer who refines the product according to the customer’s exact expectation. After a finite number of iterations, the final software package is given to the customer. In this methodology, the software is evolved as a result of periodic shuttling of information between the customer and developer.
This is the most popular development model in the contemporary IT industry. Most of the successful software products have been developed using this model – as it is very difficult (even for a whiz kid! ) to comprehend all the requirements of a customer in one shot. There are many variations of this model skewed with respect to the project management styles of the companies. New versions of a software product evolve as a result of prototyping. C. Rapid Application Development (RAD) Model The RAD modelis a linear sequential software development process that emphasizes an extremely short development cycle.
The RAD model is a “high speed” adaptation of the linear sequential model in which rapid development is achieved by using a component-based construction approach. Used primarily for information systems applications, the RAD approach encompasses the following phases: 1. Business modeling The information flow among business functions is modeled in a way that answers the following questions: What information drives the business process? What information is generated? Who generates it? Where does the information go? Who processes it? 2. Data modeling
The information flow defined as part of the business modeling phase is refined into a set of data objects that are needed to support the business. The characteristic (called attributes) of each object is identified and the relationships between these objects are defined. 3. Process modeling The data objects defined in the data-modeling phase are transformed to achieve the information flow necessary to implement a business function. Processing the descriptions are created for adding, modifying, deleting, or retrieving a data object. 4. Application generation
The RAD model assumes the use of the RAD tools like VB, VC++, Delphi etc… rather than creating software using conventional third generation programming languages. The RAD model works to reuse existing program components (when possible) or create reusable components (when necessary).
In all cases, automated tools are used to facilitate construction of the software. 5. Testing and turnover Since the RAD process emphasizes reuse, many of the program components have already been tested. This minimizes the testing and development time. D. Component Assembly Model
Object technologies provide the technical framework for a component-based process model for software engineering. The object oriented paradigm emphasizes the creation of classes that encapsulate both data and the algorithm that are used to manipulate the data. If properly designed and implemented, object oriented classes are reusable across different applicationsand computer based system architectures. Component Assembly Model leads to software reusability. The integration/assembly of the already existing software components accelerate the development process. Nowadays many component libraries are available on the Internet.
If the right components are chosen, the integration aspect is made much simpler. There are 5 phases in the development of any software. Software requirement analysis: This is the very initial and very vital stage of any application development process. The need of this stage is to gather all the details and requirements which are needed for a proper development of the application. This stage includes interview, meetings and mock discussions which make the development team more clearly about the development process. System design and analysis: This is the initial phase from where the technical stuffs are going to be implemented.
In this phase the overall structure and the nuances of the application is defined. Code Generation: In this stage all the things are made using the coding. We use different programming languages like C, C++, and Java for coding. Testing: Once the code is generated, the part of testing begins. We use different testing methodologies which are available for different levels of testing. Maintenance: After the overall development process it is our duty to give the client a basic support for future. In this phase we trained the client for using our created application and give technical support if needed.
Program Development Lifecycle When programmers build software applications, they just do not sit down and start writing code. Instead, they follow an organized plan, or methodology, that breaks the process into a series of tasks. There are many application development methodologies just as ther are many programming languages. There different methodologies, however, tend to be variations of what is called the program development life cycle (PDLC).
The program development life cycle (PDLC) is an outline of each of the steps used to build software applications.
Similarly to the way the system development lie cycle (SDLC) guides the systems analyst through development of an information system, the program development life cycle is a tool used to guide computer programmers through the development of an application. The program development lifecycle consists of six steps. Six Steps of PDLC STEP| PROCEDURE| DESCRIPTION| 1| Analyze the problem| Precisely define the problem to be solved, and write program specifications – descriptions of the program’s inputs, processing, outputs, and user interface. 2| Design the program| Develop a detailed logic plan using a tool such as pseudocode, flowcharts, object structure diagrams, or event diagrams to group the program’s activities into modules; devise a method of solution or algorithm for each module; and test the solution algorithms. | 3| Code the program| Translate the design into an application using a programming lanaguage or application development tool by creating the user interface and writing code; include internal documentation – comments and remarks within the code that explain the purpose of code statements. 4| Test and debug the program| Test the program, finding and correcting errors (debugging) until it is error free and contains enough safeguards to ensure the desired results. | 5| Formalize the solution| Review and, if necessary, revise internal documentation; formalise and complete end-user (external) documentation| 6| Maintain the program| Provide education and support to end users; correct any unanticipated errors that emerge and identify user-requested modifications (enhancements).
Once errors or enhancements are identiied, the program development life cycle begins again at Step 1. What Initiates the Program Development Cycle? As discussed in the systems analysis section the System Development Lifecycle consists of five phases: planning; analysis; design; implementation; and operation. During the analysis phase, the development team recommend how to handle software needs. Choices include purchasing packaged software, building custom software in-house, or outsourcing some or all the IT activities. If the company opts for in-house development, the design and implementation phases of the system development cycle become quite extensive.
In the design phase, the systems analyst creates a detailed set of requirements for the programmers. Once the programmers receive the requirements, the implementation phase begins. At this time, the programmer analyses the requirements of the problem to be solved. The program development cycle thus begins at the start of the implementation phase in the system development cycle. The scope requirements largely determines how many programmers work on the program development. If the scope is large, a programming team that consists of a group of programmers may develop the programs.
If the specifications are simple, a single programmer might complete all the development tasks. Whether a single programmer or a programming team, all the programmers involved must interact with users and members of the development team throughout the program development cycle. By following the steps in the program development cycle, programmers create programs that are correct (produce accurate information) and maintainable (easy to modify).
The following sections address each of the steps in the program development cycle. Step 1 – Define (Analyze the Problem)
To decide what real word problem is to be solved and how a program can do this. The decisions of what the program shoudl do. Lookng at the flow of the data, the form of the input and ouput, the process needed and the use interaction. A defining diagram helps the programmer to see the components. If I were asked to write a program whcih would comptuer the cost per square meter of living space for a house, given the dimensions of the house, the number of stories, the size of the non-living space, and the total cost o the land, I would know that any noun or adjective is input or output and any verb is process.
Design Diagram Input| Processing| Output| Width of the house| Caclulate cost per metre| Gross footage| Length of the house| Calculate living area| | Number of stories| Calculate gross footage| | Size of nonliving space| | | Selling price, less land| | | Step 2 – Outline (Design the Program) Breaking a large problem up into smaller ones. Deciding what the steps of the program are. A tool that is available to help the programmer during this step is a Flowchart, which is visual diagram of the flow of the program. Develop the Algorithm An algorithm is the step that a programmer will write that will become a program.
It is written in a form of structured language called Pseudocode. Pseudocode is language nonspecific; it could be used by any programmer to help him or her write the actual program using any programming language. Each step of your algorithm will be directly translated into a line of code when it is time to write the program using the program language. One line of the algorithm is equal to one line of code. Algorithms are written in sequential order of action and are language on-specific. If an algorithm is written correctly, any programmer using any programming language could directly translate each line of the algorithm into a line of code.
If the algorithm is correctly wrtten, the programmer knows that the program will work. It is possible to desk check the algorithm; it saves a programmer a log of time to use any algorithm and trace it to make sure that the program will be correct rather than just sitting down at the computer and writing out the program using the program language. To help write the algorithm, many programmers use other tools first. One tool is a flowchart. This is a pictorial image of the steps of a program. The majority of programmers use both – the flowchart first and then the algorithm.
Although flowcharting is not a requirement to creating an algorithm, it is a very helpful tool and I highly recommend its use. There are a number of flowcharting programs available which makes it quite easy to draw a flowchart. Two that you can dwonload from the Internet for free, are SmartDraw and RFFlow. You can also use the drawing features in Microsoft Word and Powerpoint. After creating the flowchart, you will write the algorithm using pseudocode. Pseudocode should not use any reserve word. A reserveword, also known as a keyword, is a word that is reserved or used by any specific programming language to accomplish something.
For example in C++, to show something on the computer screen, you would use the reserve word count. To do the same action using Pascal, you would use the reserve word function ‘writln’ and using Java, you would use the word ‘pintln’. We try to use normal, every day words when wrting the algorithm. An algorithm must be: * Be lucid, precise, and unambiguous * Give the correct solution in all cases * Eventually end (be complete) Step 3 – Code (Code the Program) Actually using an specific programming language to write lines of program. These lines of code are also called the listing, and are also known as the source code.
The program that you run is called the object code. When you use Word, you are using the object code. The actual lines of instruction, written by the programmer, that make Word run are the source code. Some programs execute the lines of code one by on; these types of programming languages are known as interpreters. The advantage of an intepreter is that, for a programming student, they are much easier to learn, as you are able to write one line of code and immediately test it to make sure works. The disadvantage is that these programs run slower. Basic and HTML are interpreters.
Other programming languages are compilers; they execute the entire program at one time. These programs execute much faster, but require a programmer to write an entire program to test a section. C++ is a complier. Step 4 – Test (Debug the Program) To make sure that the algorithm of your program does what it should. An error in a program is known as a bugs and the process of finding bugs is known as debugging Desk checking is looking at lines of code one by one to see if they have been written correctly and the logic is correct. Desk checking is also called tracing. The walkthrough is just when a group of people do a desk check.
Step 5 – Run/Execute (Formalize the Solution) To run the program on a computer. When you run a C++ program, first the program will complie the program. This translates the human code into binary language. When you run the program, you will do further testing. There are two main types of errors, syntax and logic errors. Syntax errors are problems with grammar, spelling, or punctuation. If you have left of a semi colon or added one where you shouldn’t have or misspelled a reserve word, these are all syntax errors. These are the easiest one to find because the program itself helps you to find them.
After the program’s translator runs, the linker runs. The linker portion of the software connects your program with lines of code that are pre-written. larger numbers of files of this code are available in libraries. Libraries that can be linked to your code take a lot of work away from you as a programmer. Logic errors are errors that make a program’s results incorrect. These are much more difficult to find. No compiler will stop and tell you that you have a logic error. To the computer, which is a stupid thing that only follows orders, thre is nothing incorrect about a logic error.
You, the programmer, need to find the logic errors by yourself. An example would be meaning to add two numbers together and to then multiply the results, but writing the formula without the required parentheses. (2+3) * 5 = 25, but 2 + 3 * 5 = 17 … a very different result. Another type of error which is common in C++ is run time error. One type of run time error is called linking error. If, in your computer program, you referrred to wantign to use some code in a library and that library was not on your computer for some reason, you would get a run time message stating that the program could not run.
Another type of run time error would be a program that tires to divide some number by zero. Dividing by zero is a illegal operation. Step 6 – Document and Maintain the Program To Document is to put togther all of the materials that have been generated throughout the PDLC process. All of the flowcharts, messages, algorithms, lines of code, and the user manuals are part of this documentation. Internal documentation is used by other programmers to help them know why you did something a certain way or tell them how you wrote a program.
Since many programmers work on teams, it is very important to have good internal documentation so that each programmer on the team can understand each other’s work. It is also a fact that a programmer might start working on a program and then leave the company for whatever reason (or be placed onto another more urgent project).
The person who takes over that job needs to see the internal documentation so that she can pick up where the leaving programer left off. if you are a programmer who needs to update a program or correct a program you’ll not be very happy if the program is not documented. f you are in doubt, it is always better to have too much itnernal documentation than too little. External documentation includes user manuals and anything that is not the actual code or is part of the listing. This should also include materials that are placed on a website such as FAQs (frequently asked questions) and help areas. To maintain is to make sure that the program keeps running as it should and to do any needed updating or fixing. Maintenance is the longest phase of the PFLC. As users use the porgram, they will notice things that need to be fixed or updated.
No matter how many times you test a program to make sure that it will work as expected, it is only when it actually gets into the hands of the actual end user that some of these errors show up. You will continue to fix and update the program until it reaches a point where the program has become redundant or too old. At that time, maintencance stops and the PDLC is started all over again. SYSTEM DESIGN System design is the solution to the creation of a new system. This phase is composed of several systems. This phase focuses on the detailed implementation of the feasible system.
It emphasis on translating design specifications to performance specification. System design has two phases of development logical and physical design. During logical design phase the analyst describes inputs (sources), out puts (destinations), databases (data sores) and procedures (data flows) all in a format that meats the uses requirements. The analyst also specifies the user needs and at a level that virtually determines the information flow into and out of the system and the data resources. Here the logical design is done through data flow diagrams and database design.
The physical design is followed by physical design or coding. Physical design produces the working system by defining the design specifications, which tell the programmers exactly what the candidate system must do. The programmers write the necessary programs that accept input from the user, perform necessary processing on accepted data through call and produce the required report on a hard copy or display it on the screen. LOGICAL DESIGN Logical design of an information system shows the major features and also how they are related to one another. The first step of the system design is to design logical design elements.
This is the most creative and challenging phase and important too. Design of proposed system produces the details of the state how the system will meet the requirements identified during the system analysis that is, in the design phase we have to find how to solve the difficulties faced by the existing system. The logical design of the proposed system should include the details that contain how the solutions can be implemented. It also specifies how the database is to be built for storing and retrieving data, what kind of reports are to be created and what are the inputs to be given to the system.
The logical design includes input design, output design, and database design and physical design INPUT DESIGN The input design is the link between the information system and the user. It comprises the developing specification and procedures for data preparation and those steps are necessary to put transaction data into a usable form for processing data entry. The activity of putting data into the computer for processing can be achieved by inspecting the computer to read data from a written or printed document or it can occur by having people keying the data directly into the system.
The design of input focuses on controlling the amount of input required, controlling errors, avoiding delay, avoiding extra steps and keeping the process simple. The system needs the data regarding the asset items, depreciation rates, asset transfer, physical verification for various validation, checking, calculation and report generation.. The error raising method is also included in the software, which helps to raise error message while wrong entry of input is done. So in input design the following things are considered. What data should be given as input A? How the data should be arranged or coded
A? The dialogue to guide the operating personnel in providing input. A? Methods for preparing input validations and steps to follow when error occur A? The samples of screen layout are given in the appendix. OUTPUT DESIGN Computer output is the most important and direct information source to the user. Output design is a process that involves designing necessary outputs in the form of reports that should be given to the users according to the requirements. Efficient, intelligible output design should improve the system’s relationship with the user and help in decision making.
Since the reports are directing referred by the management for taking decisions and to draw conclusions they must be designed with almost care and the details in the reports must be simple, descriptive and clear to the user. So while designing output the following things are to be considered. A? Determine what information to present A? Arrange the presentation of information in an acceptable format A? Decide how to distribute the output to intended receipts Depending on the nature and future use of output required, they can be displayed on the monitor for immediate need and for obtaining the hardcopy.
The options for the output reports are given in the appendix. PHYSICAL DESIGN The process of developing the program software is referred to as physical design. We have to design the process by identifying reports and the other outputs the system will produce. Coding the program for each module with its logic is performed in this step. Proper software specification is also done in this step. MODULAR DESIGN A software system is always divided into several sub systems that makes it easier for the development. A software system that is structured into several subsystems makes it easy for the development and testing.
The different subsystems are known as the modules and the process of dividing an entire system into subsystems is known as modularization or decomposition. A system cannot be decomposed into several subsystems in any way. There must some logical barrier, which facilitates the separation of each module. The separation must be simple but yet must be effective so that the development is not affected. The system under consideration has been divided into several modules taking in consideration the above-mentioned criteria. The different modules are 1. College and Department details . Login and subject 3. Student Details 4. Exam Details DATABASE DESIGN The overall objective in the development of database technology has been to treat data as an organizational resource and as an integrated whole. DBMS allow data to be protected and organized separately from other resources. Database is an integrated collection of data. The most significant form of data as seen by the programmers is data as stored on the direct access storage devices. This is the difference between logical and physical data. Database files are the key source of information into the system.
It is the process of designing database files, which are the key source of information to the system. The files should be properly designed and planned for collection, accumulation, editing and retrieving the required information. The organization of data in database aims to achieve three major objectives: – A? Data integration. A? Data integrity. A? Data independence. The proposed system stores the information relevant for processing in the MS SQL SERVER database. This database contains tables, where each table corresponds to one particular type of information.
Each piece of information in table is called a field or column. A table also contains records, which is a set of fields. All records in a table have the same set of fields with different information. There are primary key fields that uniquely identify a record in a table. There are also fields that contain primary key from another table called foreign keys. NORMALIZATION Normalization is a technique of separating redundant fields and braking up a large table in to a smaller one. It is also used to avoid insertion, deletion and updating anomalies.
All the tables have been normalized up to the third normal form. In short the rules for each of the three normal forms are as below. A? First normal form A relation is said to be in 1NF if all the under lying domain of attributes contain simple individual values. A? Second normal form The 2NF is based on the concept of full functional dependency. A relation said to be in 2NF if and only if it is in 1NF and every non-key attribute is fully functionally dependent on candidate key of the table. A? Third normal form The 3NF is based on the concept of transitive dependency. A relation in 2NF s said to be in 3NF if every non-key attribute is non-transitively. CODING The goal of the coding phase is to translate the design. The aim in this phase is to implement the design in the best possible manner. Well known code can reduce the testing and maintenance effort. During coding, the focus should on developing programs that are easy to read and understand and not simply on developing the programs that are easy to write. Simplicity and clarity should be strived for during the code phase. An important concept that help the understandability of the programs is structured programming.
The program that should be organized as a sequence of statements and during execution of the statements is executed in the sequence given in the program. There are many different criteria for judging of the program, execution time and required memory. System Design Considerations The system design process is not a step-by-step adherence of clear procedures and guidelines. Though, certain clear procedures and guidelines have emerged in recent days,But still much of design work depends on knowledge and experience of the designer. When designer starts working on system design, he will face different type of problems.
Many of these will be due to constraints imposed by the user or limitations of the hardware and software available in the market. Sometimes, it is difficult to enumerate the complexity of the problems and solutions there of since the variety of likely problems is so great and no solutions are exactly similar. However, following considerations should be kept in mind during the system designing phase: Design Objectives The primary objective of the design of course, is to deliver the requirements as specified in the feasibility reports. In general the following design objectives should be kept in mind.
Practicality The system must be stable and can be operated by people with average. Efficiency This involves accuracy, timeliness and comprehensiveness to the system output. Cost It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy all the requirements. Flexibility The system should be modifiable depending on the changing needs of the user. Such modifications should not entail extensive reconstructing or recreation of software. It should also be portable to different computer systems. Security
This is very important aspect of the design and should cover areas of hardware reliability, fall back procedures, physical security of data and provision for detection of fraud and abuse. System design involves first logical design and then physical construction of the system. The logical design describes the structure and characteristics of features, like the outputs, inputs, files, database and procedures. The physical construction, which follows the logical design, produces actual program software, files and a working system. Major System Design Activities
Several development activities are carried out during structured design. They are database design, implementation planning, system test preparation, system interface specification, and user documentation. Database design This activity deals with the design of the physical database. A key is to determine how the access paths art to be implemented. Program design: In conjunction with database design is a decision on the programming language to be used and the flowcharting, coding, and debugging procedure prior to conversion. The operating system limits the programming languages that will run of the system.
System and program test preparation. Each aspect of the system has a separate test requirement. System testing is done after all programming and testing completed the test on system and program test requirements become a part of design specifications a prerequisite to implementation. In contrast to the system testing is acceptance testing, which puts the system through a procedure design to convince the user that the proposed system will meet the stated requirements. Acceptance testing is technically similar to system testing but politically it is different. Design Process
The computer system design process is an exercise of specifying how, the system will work. It is an iterative process, which is based on what the system will be do as shown in the feasibility report. Mainly, following five parts have been included in the system design process Output Design The starting point of the design process is the proper knowledge of system requirements which will normally be converted in terms of output. Input Design Once the output requirements have been finalized, the next step is to find out what data need to be made available to the system to produce the desired outputs.
The basic documents in which these data are available need to be identified. If necessary, these documents may have to be revised or new documents may have to be introduced. File Design Once the input data is captured in the system, these may to be preserved either for a short or long period. These data will generally be stored in files in a logical manner. The designer will have to devise the techniques of storing and retrieving data from these files. Procedure Design This step involves specifications of how processing will be performed.
In this, there are two aspects: * Computer Procedure The computer procedure will specify what functions will be carried out on computer, what will be different programs and in what sequence the programs will be run. * Non-computer procedure The non-computer procedure will specify the manual procedures for feeding input data, receiving outputs etc. Control Design The control design indicates necessary procedures which will ensure correctness of processing, accuracy of data, timely output etc. this will ensure that the system is functioning as per plan. Development and Deployment Design
Major responsibilities include system Requirement Study, Preparing System Design Document, Preparing the Program (Form) Specs, Peer Review of the Specs, Implement Quality procedures as per the QMS Document, Documentation of SRS Revalidation & Design Documents, thorough grasping of the user functionality and applying, approving the same in the project, Developing, Testing & Debugging of Forms, User Training and Implementation of the module. INPUT DESIGN(Introduction) Once the analysis and design of the system has been done, it would be necessary to identify the data that are required to be processed to produce the outputs.
Input is one of the most expensive phases of the operation of a computerized system and creates sometimes a major problem. Different type of problem with a system can usually be traced back to faulty input design method needless to say, therefore, that the input data are the lifeblood of a system and have to be analyzed and designed with utmost care and consideration. Input design features can ensure the reliability of the system and generate correct reports form the accurate data. The input design also determines whether the user can interact efficiently with the system.
Elements of Input Data Inaccurate input data are the most common cause of errors in data processing. Errors entered by data entry operators can be controlled by input design. Input data are collected and organized into groups of similar data. Once identified, appropriate input media are selected for processing. Input Data The goal of designing input data is to make data entry as easy, logical and error free from errors as possible. In entering data, operators need to know the following: * The allocated space for each field. * Field sequence, which much match that in the source document. The format in which data fields are entered for example, filling out the date field is required through the edited format mm/dd/yy. * When we approach input data design, we design the source document. Let us elaborate on each step. Source Documents Source data are captured initially on original paper or a source document. For example, a cheque written against an account is a source document. When it reaches the bank, it is encoded with special magnetic ink character recognition so that a reader that is part of the information system of the bank can process it.
Therefore, source documents initiate a processing cycle as soon as they are entered into the system. s may be entered into the system from punch cards, from diskettes, or even directly through the keyboard. A source document should be logical and easy to understand. Each area in the form should be clearly identified and should specify for the user what to write and where to write it. A source document may or may not be retained in the proposed system. Thus, each source document may be evaluated in terms of.
Its continued use in the proposed system,The extent of modification for the proposed system & Replacement by an alternative source document. Input Design Guidelines The design of input play very significant role in getting the correct output. It covers al phases of input from creation of initial data (original recording) to actual entering the data to the system for processing. The input design is the link that ties the information system into the world of its users. Some features of design may vary depending on whether the system is batch-oriented or on-line. Here, we will discuss the various objectives of input design.
They focus on: * Controlling amount of input * Avoiding delay * Avoiding errors in data * Avoiding extra steps * Keeping the process simple Each of the five objectives of input design is briefly discussed below: Controlling Amount of Data An effective design controls the quantity of data for input for the following reasons: Firstly, data preparation and data entry operations depend on people. Since labor costs are high, the cost or preparing and entering data is also high. It is quite evident, then that reducing data requirements mean lowering costs through reduced labor expense.
Secondly, the input phase of computing can be slow process and take many times longer than that needed by computers to carry out their tasks. In fact, the computer itself may sit idle until data is prepared and input for processing. By reducing input requirements, the analyst will speed the entire process from data capture to processing to provide result to users. Avoiding Delay When processing is delayed owing to data preparation or data entry, the cause is called a bottleneck. Avoid bottlenecks when designing input should always be one of the objectives of the analyst. Avoiding Errors in Data
The third objective deals with errors. In one sense, the rate at which errors occur is dependent on the quantity of data. Since the lower the amount of data is inputted, there are fewer opportunities for the error to occur. Firstly, the analyst can reduce this number by reducing the volume of data dust must be entered for each transaction. Secondly, the analyst can also affect error rates of an operation through design. The manner in which data must be entered can reduce the chance of errors. Still, a third aspect of error control is the need to detect errors when they do occur.
Checks and balances in the data entry programs, called input validation techniques, also detect errors input. OUTPUT DESIGN (Introduction) Presenting the data processed by a computer-based information system in an attractive and usable form has become very essential these days’ success and acceptance of a system to some extent depends on good presentation. Therefore, system analyst must know fully how to design output report in an attractive way. Many new output devices are being introduced in the market because of recent development in computer technology.
System analyst must be aware of these new technologies and try to use these new output devices if possible. Currently, excellent graphic displays are widely available. Speech output systems are also fast emerging. There are three main reasons why outputs from the computer are required. They are: * For communication to the persons concerned. * For re-input to the computer for being connected with other data and further processing. * For permanent storage. Types of Output: Outputs of a system can take different forms. The most common are reports, displays on screen, printed forms etc. he outputs also vary in terms of their contents, type of stationery. Frequency and timing etc. besides, due consideration also need to be given as to who will use the output and for what purpose. All these points must be kept in mind while designing outputs so that the objectives of the system are met in the best possible way. Outputs of a data-processing system can be placed into two categories: * Application Output * Operating Output Application Output These are the outputs desired out of the system to meet its objectives. These are of three types: * Output as a basis for decision-making.
This type of output is generally required by management for decision-making purposes. * Output as a requirement to meet a functional objective. Invoices, Excise Gate Pass, Purchase Orders are the examples of such output. * Statutory outputs: All organization is required to produce a certain amount of reports and forms as required by law. Operating Output These outputs are mainly generated for use of EDP staff and give various indications as to how the system operates. System logs, error messages, status indicators etc. are the examples of such output.
These types of output are not concerned for the users. SYSTEM TESTING AND IMPLEMENTATION SYSTEM TESTING System testing is a critical aspect of Software Quality Assurance and represents the ultimate review of specification, design and coding. Testing is a process of executing a program with the intent of finding an error. A good test is one that has a probability of finding an as yet undiscovered error. The purpose of testing is to identify and correct bugs in the developed system. Nothing is complete without testing. Testing is the vital to the success of the system.
In the code testing the logic of the developed system is tested. For this every module of the program is executed to find an error. To perform specification test, the examination of the specifications stating what the program should do and how it should perform under various conditions. Unit testing focuses first on the modules in the proposed system to locate errors. This enables to detect errors in the coding and logic that are contained within that module alone. Those resulting from the interaction between modules are initially avoided. In unit testing step each module has to be checked separately.
System testing does not test the software as a whole, but rather than integration of each module in the system. The primary concern is the compatibility of individual modules. One has to find areas where modules have been designed with different specifications of data lengths, type and data element name. Testing and validation are the most important steps after the implementation of the developed system. The system testing is performed to ensure that there are no errors in the implemented system. The software must be executed several times in order to find out the errors in the different modules of the system.
Validation refers to the process of using the new software for the developed system in a live environment i. e. , new software inside the organization, in order to find out the errors. The validation phase reveals the failures and the bugs in the developed system. It will be come to know about the practical difficulties the system faces when operated in the true environment. By testing the code of the implemented software, the logic of the program can be examined. A specification test is conducted to check whether the specifications stating the program are performing under various conditions.
Apart from these tests, there are some special tests conducted which are given below: Peak Load Tests: This determines whether the new system will handle the volume of activities when the system is at the peak of its processing demand. The test has revealed that the new software for the agency is capable of handling the demands at the peak time. Storage Testing: This determines the capacity of the new system to store transaction data on a disk or on other files. The proposed software has the required storage space available, because of the use of a number of hard disks.
Performance Time Testing: This test determines the length of the time used by the system to process transaction data. In this phase the software developed Testing is exercising the software to uncover errors and ensure the system meets defined requirements. Testing may be done at 4 levels A? Unit Level A? Module Level A? Integration & System A? Regression UNIT TESTING A Unit corresponds to a screen /form in the package. Unit testing focuses on verification of the corresponding class or Screen. This testing includes testing of control paths, interfaces, local data structures, logical decisions, boundary conditions, and error handling.
Unit testing may use Test Drivers, which are control programs to co-ordinate test case inputs and outputs, and Test stubs, which replace low-level modules. A stub is a dummy subprogram. MODULE LEVEL TESTING Module Testing is done using the test cases prepared earlier. Module is defined during the time of design. INTEGRATION & SYSTEM TESTING Integration testing is used to verify the combining of the software modules. Integration testing addresses the issues associated with the dual problems of verification and program construction.
System testing is used to verify, whether the developed system meets the requirements. REGRESSION TESTING Each modification in software impacts unmodified areas, which results serious injuries to that software. So the process of re-testing for rectification of errors due to modification is known as regression testing. Installation and Delivery: Installation and Delivery is the process of delivering the developed and tested software to the customer. Refer the support procedures. Acceptance and Project Closure: Acceptance is the part of the project by which the customer accepts the product.
This will be done as per the Project Closure, once the customer accepts the product, closure of the project is started. This includes metrics collection, PCD, etc. SYSTEM IMPLEMENTATION Implementation includes all those activities that take place to convert from the old system to the new. The old system consists of manual operations, which is operated in a very different manner from the proposed new system. A proper implementation is essential to provide a reliable system to meet the requirements of the organizations. An improper installation may affect the success of the computerized system.
IMPLEMENTATION METHODS: There are several methods for handling the implementation and the consequent conversion from the old to the new computerized system. The most secure method for conversion from the old system to the new system is to run the old and new system in parallel. In this approach, a person may operate in the manual older processing system as well as start operating the new computerized system. This method offers high security, because even if there is a flaw in the computerized system, we can depend upon the manual system. However, the cost for maintaining two systems in parallel is very high.
This outweighs its benefits. Another commonly method is a direct cut over from the existing manual system to the computerized system. The change may be with in a week or with in a day. There are no parallel activities. However, there is no remedy in case of a problem. This strategy requires careful planning. A working version of the system can also be implemented in one part of the organization and the personnel will be piloting the system and changes can be made as and when required. But this method is less preferable due to the loss of entirety of the system. IMPLEMENTATION PLAN:
The implementation plan includes a description of all the activities that must occur to implement the new system and to put it into operation. It identifies the personnel responsible for the activities and prepares a time chart for implementing the system. The implementation plan consists of the following steps. o List all files required for implementation. o Identify all data required to build new files during the implementation. o List all new documents and procedures that go into the new system. The implementation plan should anticipate possible problems and must be able to deal with them.
The usual problems may be missing documents; mixed data formats between current and files, errors in data translation, missing data etc. Conclusion : The main objective of this study was to provide a solution to the problem at school Kigali International School, in its many difficulties in managing teachers, courses and students. This objective was successfully achieved for a practical solution it is possible to implement SMS at Kigali International School. But due to the limited time it is still a prototype which once improved can be successful for such Kind of schools. References: I. BOOKS 1.
Saint JOSEPH Computer learning Center (System Analysis & Design e- Book) page 5 2. Whitten & Bently, 2007, Systems analysis and design methods, 7th edition, McGraw-Hill,chap. 1 3. Whitten & Bently, 2007, Systems analysis and design methods, 7th edition, McGraw-Hill ,chap3 4. Whitten Bentley, «Systems analysis and design methods 7th edition», p. 70 II. WEBOGRAPHY 1. http://en. wikipedia. org/wiki/Informationtechnology 2. http://searchdatamanagement. techtarget. com/sDefinition/0,,sid91gci211902,00. html 3. http://www. learnthat. com/define/view. asp? id=2348 4. http://www. answers. com/topic/website