19-10-2016, 04:17 PM
1459932600-Junaidproject1.docx (Size: 5.03 MB / Downloads: 5)
Introduction:
One of the most important steps involved in creating a school websiteis deciding what content will be included and how it will be organized. Building a school website provides a unique addition tothe curriculum. In the development phase, students and teachers should discuss the kind of materials they want to add to the site.
Application:
This school website is developed to select and manage all of the information of school. Gives all the necessary datato the user, so that they can get to know all the relative information they want to know. It’s a simple school website for primary school.
System Requirements:
The system services and goals are established by consultation with system user. They are then defined in details and serve as a system specification. System requirement are those on which the system runs.
Software Requirements:
• Text Editor (NetBeans)
• Server (XAMP)
• Browser
Minimum Hardware Requirements:
• Pentium Processors
• 512 MB RAM
• 40 GB Hard Disk
Note: Servers and Text Editors need to be installed and configured properly in order to get the required outputs of the inputs.
HTML and CSS was used for the designing of the Websites.
PHP was used as Server scripting language.
MySQL was used as database.
AIMS & OBJECTIVES OF THE STUDY
Objective:
School are the essential part of our lives, providing the basic education to people suffering from various ailments, which may be due to change in climatic conditions, increased work-load, emotional trauma stress etc.
Thus keeping the working of the manual system as the basis of our project. We have developed an automated version of the manual system, named as “school website”.
The main aim of our project is to provide a paper-less system up to 90%. It also aims at providing low-cost reliable automation of the existing systems. The system also provides excellent security of data at every level of user-system interaction and also provides robust & reliable storage facilities.
SDLC
System development life cycle means combination of various activities. In other words, we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system development life cycle means software development life cycle.
Following are the different phases of software development cycle:
• Feasibility study
• System analysis
• System design
• Coding
• Testing
• Implementation
• Maintenance
SYSTEM ANALYSIS
It is the most creative and challenging phase of the system life cycle. The analysis phase is used to design the logical model of the system whereas the design phase is used to design the physical model.
Many things are to be done in this phase. we began the designing process by identifying forms, reports and the other outputs the system will produce. Then the specify data on each were pinpointed. we sketched the forms or say, the displays, as expected to appear, on paper, so it serves as model for the project to begin finally we design the form on computer display, using one of the automated system design tool, that is dreamweaver.
After the forms were designed, the next step was to specify the data to be inputted, calculated and stored individual data items and calculation procedure were written in detail. File structure such as paper files were selected theprocedures were written so as how to process the data and procedures the output during the programming phase.
Output design means what should be the format for presenting the results. It should be in most convenient and attractive format for the user. The input design deals with what should be the input to the system and thus prepare the input format. File design deals with how the data has to be stored on physical devices. Process design includes the description of the procedure for carrying out operations on the given data.
Feasibility Study:
A feasibility analysis involves a detailed assessment of the need, value and practicality of a proposed enterprise, such as systems development. The process of designing and implementing record keeping systems has significant accountability and resource implications for an organization. Feasibility analysis will help you make informed and transparent decisions at crucial points during the developmental process to determine whether it is operationally, economically and technically realistic to proceed with a particular course of action.
Most feasibility studies are distinguished for both users and analysts. First, the study often presupposes that when the feasibility document is being prepared, the analyst is in a position to evaluate solutions. Second, most studies tend to overlook the confusion inherent in system development – the constraints and the assumed attitudes.
Technical Feasibility:
Technical feasibility centers around the existing computer system (hardware, software, etc.) and to what extend it can support the proposed addition. For example, if the current computer is operating at 80 percent capacity – an arbitrary ceiling – then running another application could overload the system or require additional hardware. This involves financial considerations to accommodate technical enhancements. If the budget is a serious constraint, then the project is judged not feasible.
Operational Feasibility:
People are inherently resistant to change, and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have toward the development of a computerized system. It is common knowledge that computer installations have something to do with turnover, transfers, retraining, and changes in employee job status. Therefore, it is understood that the introduction of a candidate system requires special effort to educate, sell and train the staff on new ways of conducting business.
Cost/ Benefit Analysis:
Developing an IT application is an investment. Since after developing that application it provides the organization with profits. Profits can be monetary or in the form of an improved working environment. However, it carries risks, because in some cases an estimate can be wrong. And the project might not actually turn out to be beneficial.
Cost benefit analysis helps to give management a picture of the cost, benefits and risks. It usually involves comparing alternate investments. Cost benefit determines the benefits and savings that are expected from the system and compares them with the expected costs.
In performing cost and benefit analysis it is important to identify cost and benefits factors. Cost and benefits can be categorized into the following categories:
(i) Development Costs – Development costs is the costs that are incurred during the development of the system. It is one-time investment.
(ii) Operating Costs – Operating Costs are the expenses required for the day to day running of the system. Examples of Operating Costs Are Wages, Supplies and Overheads.
(iii) Hardware/Software Costs – It includes the cost of purchasing or leasing of computers and its peripherals. Software costs involves required S/W costs.
(iv)Personnel Costs – It is the money spent on the people involved in the development of the system.
(v)Facility Costs – Expenses that are incurred during the preparation of the physical site where the system will be operational. These can be wiring, flooring, acoustics, lightning, and air-conditioning.
(vi)Supply Costs – These are variable costs that are very proportionately with the amount of use of paper, ribbons, disks, and the like.
Planning and Scheduling
Planning and scheduling is a complicated part of software development. Planning, for my purpose, can be thought of as determining all the small tasks that must be carried out in order to accomplish the goal. Planning also takes into account, rules, and known as constraints, which controls when certain tasks can or cannot happen? Scheduling can be thought of as determining whether adequate resources are available to carry out the plan.
Planning was done by my team members and pert chart and gantt chart was employed for the purpose of timely completion of the project.
Further the software engineering methodology and development process was analyzed by our development team and my guide.
Thirdly the technology to be used was decided by the team members again.
Fourthly the testing methodology and pattern was decided.
At last the scope of enhancement and versioning was discussed.
Gantt Chart:
This is a tabular chart indicating activities on one side and time duration on other side. Activities also indicate milestone at regular intervals so that it is possible to evaluate progress at the time milestone to check achievement. In case there is discrepancy then additional resources, fresh planning and re-evaluation of the project is done. This also helps to identify parallel activities so that requirement at any point of time can be evaluated.
Conceptual model
Data Flow Diagrams:
A data flow diagram is a graphical representation or technique depicting information flow and transform that are applied as data moved from input to output. The DFD are partitioned into levels that represent increasing information flow and functional details. The processes, data store, data flow, etc are described in Data Dictionary.
ER-diagram
An entity-relationship diagram (ERD) is a data modeling technique that graphically illustrates an information system’s entities and the relationships between those entities. An ERD is a conceptual and representational model of data used to represent the entity framework infrastructure.
The elements of an ERD are:
• Entities
• Relationships
• Attributes
Entity
A data entity is anything real or abstract about which we want to store data. Entity types fall into five classes: roles, events, locations, tangible things or concepts. E.g. employee, payment, campus, book. Specific examples of an entity are called instances. E.g. the employee John Jones, Mary Smith's payment, etc.
Relationship
A data relationship is a natural association that exists between one or more entities. E.g. Employees process payments.
Attribute
A data attribute is a characteristic common to all or most instances of a particular entity. Synonyms include property, data element, field. E.g. Name, address, Employee Number, pay rate are all attributes of the entity employee. An attribute or combination of attributes that uniquely identifies one and only one instance of an entity is called a primary key or identifier. E.g. Employee Number is a primary key for Employee.
Steps involved in creating an ERD include:
1. Identifying and defining the entities
2. Determining all interactions between the entities
3. Analyzing the nature of interactions/determining the cardinality of the relationships
4. Creating the ERD
Data Dictionary
A data dictionary lists all data items appearing in the DFD model of a system. The data items listed include all data flows and the contents of all data stores appearing on the DFDs in the DFD model of a system. A data dictionary lists the purpose of all data items and the definition of all composite data items in terms of their component data items.
For the smallest units of data items, the data dictionary lists their name and their type. Composite data items can be defined in terms of primitive data items using the following data definition operators:
+: denotes composition of two data items, e.g. a+b represents data a and b.
[,,]: represents selection, i.e. any one of the data items listed in the brackets can occur. For example, [a,b] represents either a occurs or b occurs.
(): the contents inside the bracket represent optional data which may or may not appear. e.g. a+(b) represents either a occurs or a+boccurs.
{}: represents iterative data definition, e.g. {name}5 represents five name data. {name}* represents zero or more instances of name data.
=: represents equivalence, e.g. a=b+cmeans that a represents b and c.
/* */: Anything appearing within /* and */ is considered as a comment.
Importance of data dictionary
A data dictionary plays a very important role in any software development process because of the following reasons:
• A data dictionary provides a standard terminology for all relevant data for use by the engineers working in a project. A consistent vocabulary for data items is very important, since in large projects different engineers of the project have a tendency to use different terms to refer to the same data, which unnecessary causes confusion.
• The data dictionary provides the analyst with a means to determine the definition of different data structures in terms of their component elements.