Anda di halaman 1dari 23


I take this opportunity to present my votes of thanks to all those guidepost who really acted as lightening pillars to enlighten our way throughout this project that has led to successful and satisfactory completion of this study. We are really grateful to our teacher for providing us with an opportunity to undertake this project in this university and providing us with all the facilities. We are highly thankful to Mr. AMAN KAMBOJ for his active support, valuable time and advice, whole-hearted guidance, sincere cooperation and pains-taking involvement during the study and in completing the assignment of preparing the said project within the time stipulated. Lastly, We are thankful to all those, particularly the various friends , who have been instrumental in creating proper, healthy and conductive environment and including new and fresh innovative ideas for us during the project, their help, it would have been extremely difficult for us to prepare the project in a time bound framework.

Devika Nag B.Tech-C.SE 7th Sem Lovely Professional University Phagwara, Punjab

Organization Overview Profile of the Problem Existing System Introduction Existing Software DFD for present system Whats new in the system to be developed Problem Analysis Product definition Feasibility Analysis Project Plan Software Requirement Analysis Introduction General Description Specific Requirements Design System Design Design Notations Detailed Design Flowcharts Pseudo code


The name of my organization is Lovely Professional University (Lpu). It has a 600 + Acres Campus: A technology driven campus, spreed over 600 + acres of lush green area on NH-1 at the entry of Jalandhar city. LPU provides a Professional learning Environment that acts as a catalyst for the exponential growth of students academics as well as extracurricular abilities. LPU is Indias Largest University with 25,000+ students (on one campus) from across 26 States of India and 16 Countries around the world. LPU is duly recognized by UGC and other Apex Bodies and has accreditations of various national and International bodies and associations. LPU has a strong internationalization strategy where LPU wants to be regarded as a university with a global perspective. LPU has 25+ international tie-ups.


The profile of the problem is that in previous time, counseling of any university or colleges was held through paper work, that means for attending that counseling we had to arrived on the place where university/colleges is located. But now we can track student and perents contacts at the individual level. So with the help of counseling system we can solve the problem through: Referral Tracking:- Track referrals to and from outside professionals as well as

referrals made internally within your organization. Simultaneously track multiple referrals for individual students
Guideince Curriculum:-With the Deep Well Data Service (DWDS) Elementary

Counseling Data System, counselors are able to track their delivered curriculum by date.
Counselor Time Sheet:- Counselors can track their time spent in the four

objective areas of Individual Planning, System Support, Curriculum Development, and Responsive Service. These categories can be added to or modified to meet the needs of your project.


Introduction:Present system or Existing system of Counseling Management System working manually or computerized in a building. Therefore all types works are maintain in building. So maintain all the counseling procedure very difficult. If we are reporting, then we need go to the University and get a form for reporting and fill the form and submit in the queue conditions. Then verify there form by the university and maintain the record in computer or register. The system is mainly related to online counseling management system. Which is developing an online web based application system, it is necessary to make a thorough study of the existing system .There is no online Counseling Management System .The all the information not maintains globally. Therefore to maintain all the information of university is very difficult. Limitations of the Existing System: The maintenance of various records and procedure of reporting are being done manually by the counseling department. This leads to many drawbacks some of which are: It is a time consuming process. Proper arrangements should be made before and after the examination -which is both money spending and time consuming. As the number of students increases counseling process becomes more and more difficult. Not globally maintain the information

Evaluating of answer sheets also consumes heavy amount of time. Difficult to management the all types of information of college or university.

Existing Software: There are a number of attributes of software that can serve as requirements. It is important
that required attributes by specified so that their achievement can be objectively verified. The following items provide a partial list of examples.

The input system will allow for inputting numbers, operands, special symbols and letters of the alphabets.

DFD of present system:-

0 Level Diagram

1 Level Diagram

2 Level Diagram

Whats new in the system to be developed:-

Problem Analysis

Product definition:-

C#.NET C# language is intended to be a simple, modern, general-purpose, object-oriented programming language.

The language, and implementations thereof, should provide support for software

engineering principles such as strong type checking, array bounds checking, detection of attempts to use uninitialized variables, and automatic garbage collection. Software robustness, durability,and programmer productivity are important.
The language is intended for use in developing software components suitable for

deployment in distributed environments.

Source code portability is very important, as is programmer portability, especially for

those programmers already familiar with C and C++. Support for internationalization is very important.
C# is intended to be suitable for writing applications for both hosted and embedded

systems, ranging from the very large that use sophisticated operating systems, down to the very small having dedicated functions.
Although C# applications are intended to be economical with regard to memory and

processing power requirements, the language was not intended to compete directly on performance and size with C or assembly language.

There are no global variables or functions. All methods and members must be declared

within classes. Static members of public classes can substitute for global variables and functions. Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts.
C# supports a strict Boolean datatype, bool. Statements that take conditions, such as

while and if, require an expression of a type that implements the true operator, such as the boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing

a to be an int, or a pointer. C# disallows this "integer meaning true or false" approach on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of common programming mistakes in C or C++ such as if (a = b) (use of assignment = instead of equality ==). In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object , or to a random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack.
Code that is not marked as unsafe can still store and manipulate pointers through the

Managed memory cannot be explicitly freed; instead, it is automatically garbage

collected. Garbage collection addresses the problem of memory leaks by freeing the programmer of responsibility for releasing memory which is no longer needed.

In addition to the try...catch construct to handle exception. Multiple inheritance is not supported, although a class can implement any number of

interfaces. This was a design decision by the language's lead architect to avoid complication and simplify architectural requirements throughout CLI. C# is more type safe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. There are no implicit conversions between booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default. Starting with version 4.0, C# supports a "dynamic" data type that enforces type checking at runtime only. Enumeration members are placed in their own scope.
C# provides properties as syntactic sugar for a common pattern in which a pair of

methods, accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class. Full type reflection and discovery is available.

C# currently (as of version 4.0) has 77 reserved words.

Checked exceptions are not present in C#. This has been a conscious decision based on

the issues of scalability and versionability.

Feasibility Analysis: Feasibility is the determination of whether or not a project is worth doing. The process followed in making this determination is called a feasibility study. In other words a feasibility study is carried out to select the best system that meets performance requirements. Once it has been determined that a project is feasible, the analyst can go ahead and prepare the project specification which finalizes project requirements. Generally, feasibility studies are undertaken within tight time constraints and normally culminate in a written and oral feasibility

The contents and recommendations of such a study will be used as a sound basis for deciding whether to proceed, postpone or cancel the project. Thus, since the feasibility study may lead to the commitment of large resources, it becomes necessary that it should be conducted competently and that no fundamental errors of judgment are made. In the conduct of the feasibility study, the analyst will usually consider seven distinct, but interrelated types of feasibility. Three of them, which are used hugely, are as follows: Technical Feasibility

Operational Feasibility

Economic Feasibility

This is concerned with specifying equipment and software that will successfully satisfy

the user requirement. The technical needs of the system may vary considerably, but might include: The facility to produce outputs in a given time. Response time under certain conditions. Ability to process a certain volume of transaction at a particular speed. Facility to communicate data to distant location.

In examining technical feasibility, configuration of the system is given more importance

than the actual make of hardware.

The configuration should give the complete picture about the systems requirements:

How many workstations required? How these units are interconnected so that they could operate and communicate smoothly. What speeds of input and output should be achieved at particular quality of printing. This can be used as a basis for the tender document against which dealers and manufacturers can later make their equipment bids. Specific hardware and software products can then be evaluated keeping in view with the logical needs.
At the feasibility stage, it is desirable that two or three different configurations will be

pursued that satisfy the key technical requirements but which represent different levels of ambition and cost. Investigation of these technical alternatives can be aided by approaching a range of

suppliers for preliminary discussions. Out of all types of feasibility, technical feasibility generally is the most difficult to determine. ECONOMICAL FEASIBILITY
Economic analysis is the most frequently used technique for evaluating the effectiveness of a

proposed system. More commonly known as cost/benefit analysis; the procedure is to determine the benefits and savings that are expected from a proposed system and compare them with costs.
If benefits outweigh costs, a decision is taken to design and implement the system.

Otherwise, further justification or alternative in the proposed system will have to e made if it is to have a chance of being approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle. OPERATIONAL FEASIBILITY It is mainly related to human organizational and political aspects. The points to be considered are:

What changes will be brought with the system? What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time?

What organizational structures are disturbed?

Generally project will not be rejected simply because of operational infeasibility but such

considerations are likely to critically affect the nature and scope of the eventual recommendations. This feasibility study is carried out by a small group of people who are
familiar with information system techniques, who understand the parts of the business that

are relevant to the project and are skilled in system analysis and design process.

Project Plan
Planning and Scheduling is the detailed study of the various operations performed by a

system and their relationships within and outside of the system. During Planning and Scheduling, data are collected on the available files, decision points, and transaction handled

by the present system. The planning and decision making is the good criteria to the development of the project.

System analysis is simply uses several types of model and System Testing to their

development that is why the project get completed.

Software Requirement Analysis


General Description:-

Specific Requirement Analysis:-

Information gathering is usually the first phase of the software development project. The purpose of this phase is to identify and doucument the exact requirements for the system. The users request identifies the need for a new information system and on investigation re-defined the new information system and on investigation re-defined the new problem to be based on MIS, which supports management. The objective is to determine whether the request is valid anf feasible before a recommendation is made to build a new or existing manual system continues. The major steps are:- Defining the user requirements, Studying the present system to verify the problem, and defining the performance expected by the candidate to use requirements. Language (Front-End) : .NET FRAMEWORK 2008 Database (Back-End) : Microsoft SQL Server 2005 Operating System : Windows NT/2000/XP/VISTA


System Design Introduction: The objective of the system design is to deliver the requirements as specified in the feasibility report. System design involves first logical design (logical design) and then physical construction (detailed design) of the system. The logical design describes the structure and characteristics of features, such as the outputs, inputs, files, databases, and procedures. The physical construction produces actual program software, files, and a working system. System design goes through two phases of development: 1. Logical Design 2. Physical Design Logical Design:We know that a data flow diagram shows the logical flow of a system and defines the boundaries of the system. Logical design specifies the user need at a level of details that virtually determine the information flow into and out of the system and the required data resources. Logical design describes the inputs, outputs, database and procedures .All in a format that meets the users requirements. Physical Design:It provides the working system by defining the design specification that tells programmers exactly what that candidate system must do. In short it can state that physical design is the implementation of the logical design. Physical system design consists of the following1) Design the physical system i. Specify input, output media ii. Design the database and specify backup procedures. iii. Design physical information flow through the system and a physical design walkthrough. 2) Plan system implementation

Module Description:Online Counseling System with the fallowing modules: (1) Counseling Helps in Category wise counseling (2) Institute record covering Details regarding Institute (3) Student record - covering Details regarding Students

Design Notations:-

Detailed Design

There are some symbols that are used in the drawing of business process diagrams (data flow diagrams). These are now explained, together with the rules that apply to them. Flow diagrams in general are usually designed using simple symbols such as a rectangle, an oval or a circle depicting a processes, data stored or an external entity, and arrows are generally used to depict the data flow from one step to another. A DFD usually comprises of four components. These four components can be represented by four simple symbols. These symbols can be explained in detail as follows: External entities are represented by squares; Processes (input-processing-output) are represented by rectangles with rounded corners; Data Flows are represented by arrows; and finally, Data Stores are represented by open-ended rectangles. Data flow diagrams present the logical flow of information through a system in graphical or pictorial form. Data flow diagrams have only four symbols, which makes useful for communication between analysts and users. Data flow diagrams (DFDs) show the data used and provided by processes within a system. DFDs make use of four basic symbols. Create structured analysis, information flow, process-oriented, data-oriented, and data process diagrams as well as data flowcharts. External Entity An external entity is a source or destination of a data flow which is outside the area of study. Only those entities which originate or receive data are represented on a business process diagram. The symbol used is an oval containing a meaningful and unique identifier. Process A process shows a transformation or manipulation of data flows within the system. The symbol used is a rectangular box which contains 3 descriptive elements: Firstly an identification number appears in the upper left hand corner. This is allocated arbitrarily at the top level and serves as a unique reference.

Secondly, a location appears to the right of the identifier and describes where in the system the process takes place. This may, for example, be a department or a piece of hardware. Finally, a descriptive title is placed in the centre of the box. This should be a simple imperative sentence with a specific verb, for example 'maintain customer records' or 'find driver'. Data Flow A data flow shows the flow of information from its source to its destination. A data flow is represented by a line, with arrowheads showing the direction of flow. Information always flows to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents. Data Store A data store is a holding place for information within the system: It is represented by an open ended narrow rectangle. Data stores may be long-term files such as sales ledgers, or may be short-term accumulations: for example batches of documents that are waiting to be processed. Each data store should be given a reference followed by an arbitrary number. Resource Flow A resource flow shows the flow of any physical material from its source to its destination. For this reason they are sometimes referred to as physical flows. The physical material in question should be given a meaningful name. Resource flows are usually restricted to early, high-level diagrams and are used when a description of the physical flow of materials is considered to be important to help the analysis.

External Entities

It is normal for all the information represented within a system to have been obtained from, and/or to be passed onto, an external source or recipient. These external entities may be duplicated on a diagram, to avoid crossing data flow lines. Where they are duplicated a stripe is drawn across the left hand corner, like this. The addition of a lowercase letter to each entity on the diagram is a good way to uniquely identify them. Processes When naming processes, avoid glossing over them, without really understanding their role. Indications that this has been done are the use of vague terms in the descriptive title area - like 'process' or 'update'. The most important thing to remember is that the description must be meaningful to whoever will be using the diagram. Data Flows Double headed arrows can be used (to show two-way flows) on all but bottom level diagrams. Furthermore, in common with most of the other symbols used, a data flow at a particular level of a diagram may be decomposed to multiple data flows at lower levels. Data Stores Each store should be given a reference letter, followed by an arbitrary number. These reference letters are allocated as follows: 'D' - indicates a permanent computer file 'M' - indicates a manual file 'T' - indicates a transient store, one that is deleted after processing. In order to avoid complex flows, the same data store may be drawn several times on a diagram. Multiple instances of the same data store are indicated by a double vertical bar on their left hand edge.



ER Diagram:-