CHAPTER 1

Gathering & Analyzing Information

1.1 Introduction
This project is aimed at developing an Student Automation System for the University
of education. The system is an automation system that can be accessed throughout the
organization and outside as well with proper login provided. This system can be used as an
desktop application System of the University to manage the student. Students logging
should be able to upload their information in the form of registration.

Chapter No.1

Gathering & Analyzing info

The project has been planned to be having the view of distributed architecture, with
centralized storage of the database. The application for the storage of the data has been
planned. Using the constructs of SQL Server 2008 and all the user interfaces have been
designed using the C# technologies. The database connectivity is planned using the SQL
Connection methodology. The standards of security and data protective mechanism have
been given a big choice for proper usage. The application takes care of different modules
and their associated reports, which are produced as per the applicable strategies and
standards that are put forwarded by the administrative staff.
The entire project has been developed keeping in view of the distributed client server
computing technology, in mind. The specification has been normalized up to 3NF to
eliminate all the anomalies that may arise due to the database transaction that are executed
by the general users and the organizational administration. The user interfaces are browser
specific to give distributed accessibility for the overall system. The internal database has
been selected as SQL server 2008.The basic constructs of table spaces, clusters and indexes
have been exploited to provide higher consistency and reliability for the data storage. The
SQL server 2008 was a choice as it provides the constructs of high-level reliability and
security. The total front end was dominated using the C# technologies. At all proper levels
high care was taken to check that the system manages the data consistency with proper
business rules or validations.
1.2

Purpose
Student Automation System supports the student registration process, the

maintenance of student personal, academic and other related data.

Database maintained by this system usually contains the students personal, academic and
its other related information. It focuses on storing and processing (insertion, updation) by
using web pages. Generates student information in formatted html tables, generates the fees
invoice.
1.3

Scope
Students are admitted according to their merit in examination and their choice of

departments. Activities like Updating, Creations done in the system by the System Operator
will be maintained in the form of tables for auditing and maintaining the integrity of the
2

Chapter No.1

Gathering & Analyzing info

system. Student Automation System supports to student registration process, the

maintenance of student personal, academic and fee related data.
Definitions, Acronyms and Abbreviations

1.4

While making the Student Automation system no special acronyms and

abbreviations can be used there are simple terms can be used which is given below
i.

Admin
In this module Admin will add all the attributes, updates and delete information

about the Student Registration, they can also search courses, related books, and time table.
ii.

Student
In this module register himself and check related courses, form and fill the form

given by admin and he will search the time departments, programs, courses and they can
saw teachers with their post.
iii.

Notification
In this module student will get their registration and can see their departments with

related subjects and staff member and also new updates.

1.5

Use Cases and Usage Scenarios

The Unified Modeling Language (UML) is a standard language for specifying,

visualizing, constructing, and documenting the artifacts of software systems, as well as for
business modeling and other non-software systems. The UML represents a collection of best
engineering practices that have proven successful in the modeling of large and complex
systems.1 The UML is a very important part of developing object oriented software and the
software development process. The UML uses mostly graphical notations to express the
design of software projects. Using the UML helps project teams communicate, explore
potential designs, and validate the architectural design of the software.
1.5.1 Goals of UML

Chapter No.1

Gathering & Analyzing info

The primary goals in the design of the UML were:

1.

Provide users with a ready-to-use, expressive visual modeling language so they can

develop and exchange meaningful models.

2.

Provide extensibility and specialization mechanisms to extend the core concepts.

3.

Be independent of particular programming languages and development processes.

4.

Provide a formal basis for understanding the modeling language.

5.

Encourage the growth of the OO tools market.

6.

Support higher-level development concepts such as collaborations, frameworks,

patterns and components.

7.

Integrate best practices.

1.5.2 Why Use UML?

As the strategic value of software increases for many companies, the industry looks
for techniques to automate the production of software and to improve quality and reduce
cost and time-to-market. These techniques include component technology, visual
programming, patterns and frameworks. In particular, they recognize the need to solve
recurring architectural problems, such as physical distribution, concurrency, replication,
security, load balancing and fault tolerance. Additionally, the development for the World
Wide Web, while making some things simpler, has exacerbated these architectural problems.
The Unified Modeling Language (UML) was designed to respond to these needs.
Each UML diagram is designed to let developers and customers view a software
system from a different perspective and in varying degrees of abstraction. UML diagrams
commonly created in visual modeling tools include.
Here is now use case diagram for the Student Automation System.
1.5.3

Use Case Diagrams.

Run
App

View
Departments
View
programs

Chapter No.1

Gathering & Analyzing info

View
courses

Student

View
Faculty
Registratio
n
Registratio
n
Fig 1.1 Use Care Diagram of student Automation System

1.5.4

Usage Scenarios.
It is easy to mix up the definitions of use case and use case scenario. A use case

represents the actions that are required to enable or abandon a goal. A use case has multiple
paths that can be taken by any user at any one time. A use case scenario is a single path
through the use case. This article provides an example use case and some diagrams to help
visualize the concept.
A usage scenario, or scenario for short, describes a real-world example of how one
or more people or organizations interact with a system. They describe the steps, events,
and/or actions which occur during the interaction. Usage scenarios can be very detailed,
indicating exactly how someone works with the user interface, or reasonably highlevel describing the critical business actions but not the indicating how theyre performed.
Here is some Usage Scenario with UML Activity diagrams which can show the
process flow of the Student Automation system.
Usage Scenario for Student Automation system
1. Use case name: Registration
Description: User enters the required fields, presses register button, client program
contacts with server, server contacts with the database, database updates and sends result
to the user.
Actor: student
Pre conditions: New User
Success Outcome: Register successfully.

Fail Outcome: Register Failure.

5

Chapter No.1

Gathering & Analyzing info

2. Use case name: Login

Description: This use case describe the login process of Authorized user
Actor: Registered student
Pre conditions: must be Registered student
Success Outcome: Login successfully.

Fail Outcome: Login Failure.

3. Use case name: Search For Departments

Description: This use case describe the searching of departments
Actor: Registered student
Pre conditions: must be Registered student
Success Outcome: Search successfully.
Fail Outcome: Search Failure.
4. Use case name: View Program
Description: This use case describe the different programs related to different
departments
Actor: Registered student
Pre conditions: : must be Registered student
Success Outcome: Successfully.
Fail Outcome: Failure.

5. Use case name: Select Registration form

Description: User enters the Functional area and information and clicks Submit button,
client program contacts with server, server contacts with the database; database sends the
results to the user.
Actor: Registered student
Pre conditions: User must be Registered
Success Outcome: Find Registration

Fail Outcome: Registration Failed

successfully.
6. Use case name: Roll No
Description: student automatically get the roll no by their departments
Actor: Registered student
Pre conditions: student must be Registered
Success Outcome: register successfully.
Fail Outcome: registration Failure.
Usage Scenario for Admin
7. Use case name: Activate and Deactivate courses and faculty
Description: This Admin s Use Case in which the Use Case alter or activate or
6

Chapter No.1

Gathering & Analyzing info

deactivate the both courses and faculty

Actor: Any user
Pre conditions: User must have Authorization
Success Outcome: User login successfully. Fail Outcome: Login Failure.
Usage Scenario for student
Run App

Register himself
and watch
departments
Can see programs
Fig 1.2 Usage Scenario for Student
1.6

Supplementary Requirements.

The supplementary requirements are part of software system specifications which

covers the non-functional requirements that the software system need to address.
For example - the security features the system is suppose to cover, the auditing
features etc. There could be a long list based on the context of the system in scope like the
scalability, performance, no-of usurers supported etc.
1.6.1

Usability.

The term usability in the context of creating software represents an approach that
puts the user, rather than the system, at the centre of the process. This philosophy, called
user-centred design, incorporates user concerns and advocacy from the beginning of the
design process and dictates that the needs of the user should be foremost in any design
decisions.
In designing of this Student automation system it is taken care that it can be easy to
use no more complex abilities.
1.6.2

Reliability.

Software Reliability is the probability of failure-free software operation for a

specified period of time in a specified environment. So it is also taken care while making

Chapter No.1

Gathering & Analyzing info

unique job portal that it should be reliable thats why it is developed in most advanced
language C#.
1.6.3

Supportability.

Supportability is also very important factor that a system which can designed it can
be supportable in most of environment. Unique job portal is a website which has not too
much supportably issues because it can run on simple browser.
1.6.4 System Requirements.

Processor:

Intel Pentium 4 or Higher

Processor speed:

1.7 GHZ or Higher

Hard disk drive:

40GB

Ram memory:

4GB or Higher

1.6.5 Software Requirements:

WINDOWS OS (XP / VISTA/ WIN 7)

SQL Server 2008 Enterprise Edition
Visual Studio
Adobe Photoshop