software engineering lab€¦ · web viewfostering a scientific temper among students by means of a...

Software Engineering Lab

Software EngineeringLab

TE (COMPUTER ENGINEERING) Semester - V

Laboratory Manual

Department of Computer EngineeringR. C. Patel Institute of Technology, Shirpur

VISION & MISSIONR. C. Patel Institute of Technology, Shirpur


Institute Vision:

To achieve excellence in engineering education with strong ethical values.Mission: To impart high quality Technical Education through:

Innovative and Interactive learning process and high quality instructional programs.

Fostering a scientific temper among students by means of a liaison with the Academia, Industries and Government.

Preparing students from diverse backgrounds to have attitude for research and spirit of Professionalism.

Inculcating in students a respect for fellow human beings and responsibility towards the society.

Computer Engineering DepartmentVision:

To provide prominent computer engineering education with socio-moral values.Mission:

To groom students to become professionally and ethically sound computer engineers to meet the growing needs of industry and society.

R. C. Patel Institute of Technology, Shirpur


The Shirpur Education Society’sR. C. Patel Institute of Technology, Shirpur

CERTIFICATE CERCERTIFICATEThis is to certify that Mr. / Miss. ________________________________of Third Year Computer Engineering, Roll No. ______has performed practical work satisfactorily in the subject Software Engineering Lab, in the Department of Computer Engineering during the academic year 20__ -20__.

Date: / / 20 Subject Incharge

Place: Shirpur

Principal Head of Department

CONTENTS

Expt. No Experiment Title Page No

1Study of UML (Unified Modeling Language) in brief. 6

2Developing Library Management System (Library Management Software) using 37



Classical Life Cycle model.

3Developing University Result Management System using Classical Life Cycle model. 49

4Developing bank ATM (Automated Teller Machine) System using Classical Life Cycle model.

64

5Developing Hospital Management System using Classical Life Cycle model. 79

6Developing College Admission System using Classical Life Cycle model. 92



Laboratory ReportExperiment No - 01

Batch -

Date of Experiment:__________ Date of Submission:__________

Title: ___________________________________________________________Evaluation 1) Attendance [2] ----------------2) Lab Performance [2] ----------------3) Oral [1] ----------------

Overall Marks [5] ----------------

Subject InchargeExperiment No.1

TITLE: Study of UML (Unified Modeling Language) in brief.

PREREQUISITE: Nil



HARDWARE CONFIGURATION / KIT:Sr. No Hardware Configuration

1 Processor NA2 RAM NA3 HDD NA4 Standard I/O devices NA

SOFTWARE CONFIGURATION:Sr. No Software Configuration

1 Operating System NA2 Rational Rose Enterprise

Edition NA

THEORY:1. DefinitionUnified Modeling Language (UML) is a standardized (ISO/IEC 19501:2005), general-purpose modeling language in the field of Software Engineering. The Unified Modeling Language includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems. Unified Modeling Language (UML) combines techniques from data modeling (Entity Relationship Diagrams), business modeling (work flows), object modeling, and component modeling. It can be used with all processes, throughout the software development life cycle, and across different implementation technologies. The UML offers a standard way to visualize a system's architectural blueprints, including elements such as: activities, actors, business processes, database schemas, (logical) components, programming language statements, reusable software components.2. HistoryThe Unified Modeling Language was developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in the 1990s. It was adopted by the Object Management Group (OMG) in 1997, and has been managed by this organization ever since. In 2000 the Unified Modeling Language was accepted by the International Organization for Standardization (ISO) as industry standard for modeling software-intensive systems. The current version of the UML is 2.4.1 published by the OMG in August 2011.3. IntroductionThe Unified Modeling Language (UML) is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct, and document the artefacts of a software intensive system. The UML is appropriate for modelling systems ranging from enterprise information



systems to distributed Web-based applications and even to hard real time embedded systems.

Even though it is expressive, the UML is not difficult to understand and to use. Learning to apply the UML effectively starts with forming a conceptual model of the language, which requires learning three major elements: the UML's basic building blocks, the rules that dictate how these building blocks may be put together, and some common mechanisms that apply throughout the language. The UML is only a language and so is just one part of a software development method.

4. Where Can the UML Be Used?The UML is proposed primarily for software-intensive systems. It has been used effectively for such areas as

Enterprise information systems Banking and financial services Telecommunications Transportation Defence/aerospace Retail Medical electronics Distributed Web-based services

The UML is not limited to modelling software. In fact, it is expressive enough to model non-software systems, such as workflow in the legal system, the structure and behaviour of a patient healthcare system, and the design of hardware.

5. Building Blocks of the UMLThe vocabulary of the UML comprises of three kinds of building blocks1. Things 2. Relationships 3. Diagrams

1. Things in the UMLThere are four kinds of things in the UML1. Structural things2. Behavioural things3. Grouping things4. Annotational thingsThese things are the basic object-oriented building blocks of the UML. You use them to write well-formed models.



1.1 Structural ThingsStructural things are the nouns of UML models. These are the mostly the static parts of a model, representing elements that are either conceptual or physical. There are seven kinds of structural things.

1.1.1 ClassesA class is a description of a set of objects that share the same attributes, operations, relationships, and semantics. A class implements one or more interfaces. Graphically, a class is rendered as a rectangle, usually including its name, attributes, and operations, as in Figure 1.

Figure 1.Student Class

1.1.2 InterfacesInterface is used to describe functionality without implementation. Interface is the just like a template where you define different functions not the implementation. When a class implements the interface it also implements the functionality as per the requirement. An interface therefore describes the externally visible behaviour of that element. An interface might represent the complete behaviour of a class or component or only a part of that behaviour. An interface defines a set of operation specifications (that is, their signatures) but never a set of operation implementations. Graphically, an interface is represented by a circle together with its name as in Figure 2.



Figure 2.Interface ImageObserver1.1.3 Collaborations

Collaboration defines an interaction and is a society of roles and other elements that work together to provide some cooperative behaviour that's bigger than the sum of all the elements. A given class might participate in several collaborations. Graphically; collaboration is represented as an ellipse with dashed lines, usually including only its name, as in Figure 3.

Figure 3.Collaborations

1.1.4 Use cases Use case is used to capture high level functionalities of a system. A use case is used to structure the behavioural things in a model. Graphically, a use case is represented as an ellipse with solid lines, usually including only its name, as in Figure 4.

Figure 4.Use cases

1.1.5 Active classes



An active class is a class whose objects own one or more processes or threads and therefore can initiate control activity. An active class is just like a class except that its objects represent elements whose behaviour is concurrent with other elements. Graphically, an active class is represented just like a class, but with heavy lines, usually including its name, attributes, and operations, as in Figure 5.

Figure 5.Active class Event Manager

1.1.6 Components A component is a physical and replaceable part of a system that conforms to and provides the realization of a set of interfaces. In a system, you'll encounter different kinds of deployment components, such as COM+ components or Java Beans, as well as components that are artefact of the development process, such as source code files. A component typically represents the physical packaging of otherwise logical elements, such as classes, interfaces, and collaborations.Graphically, a component is represented as a rectangle with tabs, usually including only its name, as in Figure 6.

Figure 6.Component orderform.java



1.1.7 Nodes Seventh, a node is a physical element that exists at run time and represents a computational resource, generally having at least some memory and, often, processing capability. A set of components may reside on a node and may also migrate from node to node. Graphically, a node is denoted as a cube, usually including only its name, as in Figure 7.

Figure 7.Server node

1.2 Behavioural ThingsBehavioural things are the dynamic parts of UML models. These are the verbs of a model, representing behaviour over time and space. In all, there are two primary kinds of behavioural things. First, an interaction is a behaviour that comprises a set of messages exchanged among a set of objects within a particular context to accomplish a specific purpose. The behaviour of a society of objects or of an individual operation may be specified with an interaction. An interaction involves a number of other elements, including messages, action sequences (the behaviour invoked by a message), and links (the connection between objects). Graphically, a message is rendered as a directed line, almost always including the name of its operation, as in Figure 8.

Figure 8.Messages1.2.1 StateA state machine is a behaviour that specifies the sequences of states an object. The behaviour of an individual class or a collaboration of classes may be specified with a state machine. A state machine involves a number of other elements, including states, transitions (the flow from state to state), events (things that trigger a transition), and activities (the response to a transition). Graphically, a state is denoted as a rounded rectangle, usually including its name and its sub states, if any, as in Figure 9.



Figure 9.State

1.3 Grouping ThingsGrouping things are the organizational parts of UML models. These are the boxes into which a model can be decomposed. In all, there is one primary kind of grouping thing, namely, packages.

1.3.1 PackageA package is a general-purpose mechanism for organizing elements into groups. Structural things, behavioural things, and even other grouping things may be placed in a package. Unlike components (which exist at run time), a package is purely conceptual (meaning that it exists only at development time). Graphically, a package is denoted as a tabbed folder, usually including only its name and, sometimes, its contents, as in Figure 10.

Figure 10.Package1.4 Annotational ThingsAnnotational things are the explanatory parts of UML models. These are the comments you may apply to describe, illuminate, and remark about any element in a model.

1.4.1 Note There is one primary kind of annotational thing, called a note. A note is simply a symbol for rendering constraints and comments attached to an



element or a collection of elements. Graphically, a note is denoted as a rectangle with a dog-eared corner, together with a textual or graphical comment, as in Figure 11.

Figure 11.Note

2. Relationships in the UMLThere are four kinds of relationships in the UML1. Dependency2. Association3. Generalization4. RealizationThese relationships are the basic relational building blocks of the UML. You use them to write well-formed models.

2.1 DependencyFirst, a dependency is a semantic relationship between two things in which a change to one thing(The independent thing) may affect the semantics of the other thing (the dependent thing). Graphically, a dependency is represented as a dashed line, possibly directed, and occasionally including a label, as in Figure 12.

Figure 12.Dependency

2.2 Associations Association describes how the elements in an UML diagram are associated. In simple word it describes how many elements are taking part in an interaction. Association is represented by a dotted line with (without) arrows on both sides. The two ends represent two associated elements as shown below. The multiplicity is also mentioned at the ends (1, * etc) to show how many objects are associated. Graphically, an association is rendered as a



solid line, possibly directed, occasionally including a label, and often containing other adornments, such as multiplicity and role names, as in Figure 13.

Figure 13.Associations

2.2.1 NameAn association can have a name, and you use that name to describe the nature of the relationship. So that there is no ambiguity about its meaning, you can give a direction to the name by providing a direction triangle that point in the direction you intend to read the name, as shown in Figure 14.

Figure 14.Association Name

2.2.2 RoleWhen a class participates in an association, it has a specific role that it plays in that relationship a role is just the face the class at the near end of the association presents to the class at the other end of the association. You can explicitly name the role a class plays in an association. In Figure 15, a Person playing the role of employee is associated with a Company playing the role of employer.



Figure 15.Association Role

2.2.3 MultiplicityAn association represents a structural relationship among objects. In many modeling situations, it's important for you to state how many objects may be connected across an instance of an association. This "how many" is called the multiplicity of an association's role and is written as an expression that evaluates to a range of values or an explicit value as shown in Figure 16. When you state a multiplicity at one end of an association, you are specifying that, for each object of the class at the opposite end, there must be that many objects at the near end. You can show a multiplicity of exactly one (1), zero or one (0..1), many (0..*), or one or more (1..*). You can even state an exact number.

Figure 16.Multiplicity

2.2.4 AggregationA plain association between two classes represents a structural relationship between peers, meaning that both classes are conceptually at the same level, no one more important than the other. Sometimes, you want to model a "whole/part" relationship, in which one class represents a larger thing (the "whole"), which consists of smaller things (the "parts"). This kind of relationship is called aggregation, which represents a "has-a" relationship, meaning that an object of the whole has objects of the part. Aggregation is



really just a special kind of association and is specified by adorning a plain association with an open diamond at the whole end, as shown in Figure 17.

Figure 17.Aggregation2.3 Generalizations Third, a generalization is a specialization/generalization relationship in which objects of the specialized element (the child) are substitutable for objects of the generalized element (the parent). In this way, the child shares the structure and the behaviour of the parent. Graphically, a generalization relationship is rendered as a solid line with a hollow arrowhead pointing to the parent, as in Figure 18.

Figure 18.Generalizations

2.4 Realizations Fourth, a realization is relationship between classifiers, wherein one classifier specifies a contract that another classifier guarantees to carry out. You'll encounter realization relationships in two places: between interfaces and the classes or components that realize them, and between use cases and the collaborations that realize them. Graphically, a realization relationship is rendered as a cross between a generalization and a dependency relationship, as Figure 19.



Figure 19.Realizations

6. UML DiagramsUML diagrams are the ultimate output of the entire discussion. All the elements, relationships are used to make a complete UML diagram and the diagram represents a system. The visual effect of the UML diagram is the most important part of the entire process. All the other elements are used to make it a complete one.

UML includes the following nine diagrams and the details are described in the following chapters. 1. Class diagram 2. Object diagram 3. Use case diagram 4. Sequence diagram 5. Collaboration diagram 6. Activity diagram 7. State chart diagram 8. Deployment diagram 9. Component diagram We would discuss all these diagrams in subsequent chapters of this Lab manual.

7. UML ArchitectureAny real world system is used by different users. The users can be developers, testers, business people, analysts and many more. So before designing a system the architecture is made with different perspectives in mind. The most important part is to visualize the system from different viewer’s perspective. The better we understand the better we make the system.

UML plays an important role in defining different perspectives of a system. These perspectives are

Design Implementation Process Deployment

And the center is the Use Case view which connects all these four. A Use case represents the functionality of the system. So the other perspectives are connected with use case.



Design of a system consists of classes, interfaces and collaboration. UML provides class diagram, object diagram to support this.

Implementation defines the components assembled together to make a complete physical system. UML component diagram is used to support implementation perspective.

Process defines the flow of the system. So the same elements as used in Design are also used to support this perspective.

Deployment represents the physical nodes of the system that forms the hardware. UML deployment diagram is used to support this perspective.

8. UML Standard Diagrams In the previous chapters we have discussed about the building blocks and other necessary elements of UML. Now we need to understand where to use those elements.

The elements are like components which can be associated in different ways to make complete UML pictures which is known as diagram. So it is very important to understand the different diagrams to implement the knowledge in real life systems.

Any complex system is best understood by making some kind of diagrams or pictures. These diagrams have a better impact on our understanding. So if we look around then we will realize that the diagrams are not a new concept but it is used widely in different form in different industries.

We prepare UML diagrams to understand a system in better and simple way. A single diagram is not enough to cover all aspects of the system. So UML defines various kinds of diagrams to cover most of the aspects of a system.

You can also create your own set of diagrams to meet your requirements. There are two broad categories of diagrams and then are again divided into sub-categories,

Structural Diagrams Behavioural Diagrams

1.Structural Diagrams The structural diagrams represent the static aspect of the system. These static aspects represent those parts of a diagram which forms the main structure and therefore stable. These static parts are represents by classes, interfaces, objects, components and nodes. The four structural diagrams are:

Class diagram



Object diagram Component diagram Deployment diagram

1.1 Class Diagrams Class diagrams are the most common diagrams used in UML. Class diagram consists of classes, interfaces, associations and collaboration. Class diagrams basically represent the object oriented view of a system which is static in nature. Active class is used in a class diagram to represent the concurrency of the system. Class diagram represents the object orientation of a system. So it is generally used for development purpose. This is the most widely used diagram at the time of system construction.

1.2 Object Diagram Object diagrams can be described as an instance of class diagram. So these diagrams are more close to real life scenarios where we implement a system. Object diagrams are a set of objects and their relationships just like class diagrams and also represent the static view of the system. The usage of object diagrams is similar to class diagrams but they are used to build prototype of a system from practical perspective.

1.3 Component Diagram Component diagrams represent a set of components and their relationships. These components consist of classes, interfaces or collaborations. So Component diagrams represent the implementation view of a system. During design phase software artifacts (classes, interfaces etc.) of a system are arranged in different groups depending upon their relationship. Now these groups are known as components. Finally, component diagrams are used to visualize the implementation.

1.4 Deployment DiagramDeployment diagrams are a set of nodes and their relationships. These nodes are physical entities where the components are deployed. This is generally used by the deployment team.

Note: If the above descriptions and usages are observed carefully then it is very clear that all the diagrams are having some relationship with one another. Component diagrams are dependent upon the classes, interfaces etc. which are part of class/object diagram. Again the deployment diagram is



dependent upon the components which are used to make a component diagrams.

2. Behavioral DiagramsAny system can have two aspects, static and dynamic. So a model is considered as complete when both the aspects are covered fully.

Behavioral diagrams basically capture the dynamic aspect of a system. Dynamic aspect can be further described as the changing/moving parts of a system. UML has the following five types of behavioral diagrams,

Use case diagram Sequence diagram Collaboration diagram State-chart diagram Activity diagram

2.1 Use case DiagramUse case diagrams are a set of use cases, actors and their relationships. They represent the use case view of a system.

A use case represents a particular functionality of a system. So use case diagram is used to describe the relationships among the functionalities and their internal/external controllers. These controllers are known as actors.

2.2 Sequence DiagramA sequence diagram is an interaction diagram. From the name it is clear that the diagram deals with some sequences, which are the sequence of messages flowing from one object to another. Interaction among the components of a system is very important from implementation and execution perspective.

2.3 Collaboration Diagram Collaboration diagram is another form of interaction diagram. It represents the structural organization of a system and the messages sent/received. Structural organization consists of objects and links.

The purpose of collaboration diagram is similar to sequence diagram. But the specific purpose of collaboration diagram is to visualize the organization of objects and their interaction.

2.4 State-chart Diagram



Any real time system is expected to be reacted by some kind of internal/external events. These events are responsible for state change of the system.

State-chart diagram is used to represent the event driven state change of a system. It basically describes the state change of a class, interface etc. State-chart diagram is used to visualize the reaction of a system by internal/external factors.

2.5 Activity DiagramActivity diagram describes the flow of control in a system. So it consists of activities and links. The flow can be sequential, concurrent or branched.

Activities are nothing but the functions of a system. Numbers of activity diagrams are prepared to capture the entire flow in a system. Activity diagrams are used to visualize the flow of controls in a system. This is prepared to have an idea of how the system will work when executed.

Note: Dynamic nature of a system is very difficult to capture. So UML has provided features to capture the dynamics of a system from different angles. Sequence diagrams and collaboration diagrams are isomorphic so they can be converted from one another without losing any information. This is also true for state-chart and activity diagram.

9. UML Class Diagram The class diagram is a static diagram. It represents the static view of an application. Class diagram is not only used for visualizing, describing and documenting different aspects of a system but also for constructing executable code of the software application. The class diagram describes the attributes and operations of a class and also the constraints imposed on the system.

The class diagrams are widely used in the modelling of object oriented systems because they are the only UML diagrams which can be mapped directly with object oriented languages.

The class diagram shows a collection of classes, interfaces, associations, collaborations and constraints. It is also known as a structural diagram.

Purpose The purpose of the class diagram is to model the static view of an application. The class diagrams are the only diagrams which can be directly



mapped with object oriented languages and thus widely used at the time of construction.

The UML diagrams like activity diagram, sequence diagram can only give the sequence flow of the application but class diagram is a bit different. So it is the most popular UML diagram in the coder community. So the purpose of the class diagram can be summarized as

Analysis and design of the static view of an application. Describe responsibilities of a system. Base for component and deployment diagrams. Forward and Reverse Engineering.

How to draw Class Diagram? Class diagrams are the most popular UML diagrams used for construction of software applications. So it is very important to learn the drawing procedure of class diagram.

Class diagrams have lot of properties to consider while drawing but here the diagram will be considered from a top level view.

Class diagram is basically a graphical representation of the static view of the system and represents different aspects of the application. So a collection of class diagrams represent the whole system.

Figure 20.Class Diagram

The following points should be remembered while drawing a class diagram



The name of the class diagram should be meaningful to describe the aspect of the system.

Each element and their relationships should be identified in advance. Responsibility (attributes and methods) of each class should be clearly

identified. For each class minimum number of properties should be specified. Because

unnecessary properties will make the diagram complicated. Use notes whenever required to describe some aspect of the diagram.

Because at the end of the drawing it should be understandable to the developer/coder.

Finally, before making the final version, the diagram should be drawn on plain paper and rework as many times as possible to make it correct. Now the following diagram is an example of an Order System of an application. So it describes a particular aspect of the entire application.

First of all Order and Customer are identified as the two elements of the system and they have a one to many relationship because a customer can have multiple orders.

We would keep Order class is an abstract class and it has two concrete classes (inheritance relationship) SpecialOrder and NormalOrder. The two inherited classes have all the properties as the Order class. In addition they have additional functions like dispatch ( ) and receive ( ). So the class diagram shown in figure 20 has been drawn considering all the points mentioned above.

10. UML Component Diagram Component diagrams are different in terms of nature and behaviour. Component diagrams are used to model physical aspects of a system.

Now the question is what are these physical aspects? Physical aspects are the elements like executables, libraries, files, documents etc. which resides in a node.

So component diagrams are used to visualize the organization and relationships among components in a system. These diagrams are also used to make executable systems.

PurposeComponent diagram is a special kind of diagram in UML. The purpose is also different from all other diagrams discussed so far. It does not describe the functionality of the system but it describes the components used to make those functionalities.



So from that point component diagrams are used to visualize the physical components in a system. These components are libraries, packages, files etc.

Component diagrams can also be described as a static implementation view of a system. Static implementation represents the organization of the components at a particular moment.

A single component diagram cannot represent the entire system but a collection of diagrams are used to represent the whole.

How to draw Component Diagram? Component diagrams are used to describe the physical artefacts of a system. This artefact includes files, executables, libraries etc.

So the purpose of this diagram is different, Component diagrams are used during the implementation phase of an application. But it is prepared well in advance to visualize the implementation details.

Initially the system is designed using different UML diagrams and then when the artefacts are ready component diagrams are used to get an idea of the implementation. This diagram is very important because without it the application cannot be implemented efficiently. A well prepared component diagram is also important for other aspects like application performance, maintenance etc. So before drawing a component diagram the following artefacts are to be identified clearly

Files used in the system. Libraries and other artefacts relevant to the application. Relationships among the artefacts.

Now after identifying the artefacts the following points needs to be followed Use a meaningful name to identify the component for which the diagram is

to be drawn. Prepare a mental layout before producing using tools. Use notes for clarifying important points.

The following is a component diagram for order management system. Here the artifacts are files. So the diagram shows the files in the application and their relationships. In actual the component diagram also contains dlls, libraries, folders etc.

In the following diagram four files are identified and their relationships are produced. Component diagram cannot be matched directly with other UML diagrams discussed so far because it is drawn for completely different purpose. So the following component diagram (figure 21) has been drawn considering all the points mentioned above.



Figure 21.Component Diagram

11. UML Deployment Diagram Deployment diagrams are used to visualize the topology of the physical components of a system where the software components are deployed.

So deployment diagrams are used to describe the static deployment view of a system. Deployment diagrams consist of nodes and their relationships. PurposeThe name Deployment itself describes the purpose of the diagram. Deployment diagrams are used for describing the hardware components where software components are deployed. Component diagrams and deployment diagrams are closely related. Component diagrams are used to describe the components and deployment diagrams shows how they are deployed in hardware.

But these two diagrams are special diagrams used to focus on software components and hardware components. So most of the UML diagrams are used to handle logical components but deployment diagrams are made to focus on hardware topology of a system. Deployment diagrams are used by the system engineers. The purpose of deployment diagrams can be described as:

Visualize hardware topology of a system. Describe the hardware components used to deploy software components. Describe runtime processing nodes.



How to draw Deployment Diagram?Deployment diagram represents the deployment view of a system. It is related to the component diagram. Because the components are deployed using the deployment diagrams. A deployment diagram consists of nodes. Nodes are nothing but physical hardware used to deploy the application.

Deployment diagrams are useful for system engineers. An efficient deployment diagram is very important because it controls the following parameters

Performance Scalability Maintainability Portability

So before drawing a deployment diagram the following artifacts should be identified:

Nodes Relationships among nodes

Figure 22.Deployment Diagram

12. UML Use Case Diagram To model a system the most important aspect is to capture the dynamic behaviour. To clarify a bit in details, dynamic behaviour means the behaviour of the system when it is running /operating.

So only static behaviour is not sufficient to model a system rather dynamic behaviour is more important than static behaviour. In UML there are five diagrams available to model dynamic nature and use case diagram is one of them. Now as we have to discuss that the use case diagram is dynamic in nature there should be some internal or external factors for making the interaction.



These internal and external agents are known as actors. So use case diagrams are consists of actors, use cases and their relationships. The diagram is used to model the system/subsystem of an application. A single use case diagram captures a particular functionality of a system.So to model the entire system numbers of use case diagrams are used.

PurposeThe purpose of use case diagram is to capture the dynamic aspect of a system. But this definition is too generic to describe the purpose. Because other four diagrams (activity, sequence, collaboration and State-chart) are also having the same purpose. So we will look into some specific purpose which will distinguish it from other four diagrams.

Use case diagrams are used to gather the requirements of a system including internal and external influences. These requirements are mostly design requirements. So when a system is analysed to gather its functionalities use cases are prepared and actors are identified. Now when the initial task is complete use case diagrams are modelled to present the outside view. So in brief, the purposes of use case diagrams can be as follows:

Used to gather requirements of a system. Used to get an outside view of a system. Identify external and internal factors influencing the system. Show the interacting among the requirements are actors.

How to draw Use Case Diagram? Use case diagrams are considered for high level requirement analysis of a system. So when the requirements of a system are analyzed the functionalities are captured in use cases.

So we can say that uses cases are nothing but the system functionalities written in an organized manner. Now the second things which are relevant to the use cases are the actors. Actors can be defined as something that interacts with the system.

The actors can be human user, some internal applications or may be some external applications.

So in a brief when we are planning to draw an use case diagram we should have the following items identified.

Functionalities to be represented as an use case Actors Relationships among the use cases and actors.



Use case diagrams are drawn to capture the functional requirements of a system. So after identifying the above items we have to follow the following guidelines to draw an efficient use case diagram.

The name of a use case is very important. So the name should be chosen in such a way so that it can identify the functionalities performed.

Give a suitable name for actors. Show relationships and dependencies clearly in the diagram. Do not try to include all types of relationships. Because the main purpose of

the diagram is to identify requirements. Use note whenever required to clarify some important points.

Actor NotationAn actor can be defined as some internal or external entity that interacts with the system. Actor is used in a use case diagram to describe the internal or external entities.

Figure 23.Actor Notation

Figure 24.Use case Diagram



13. UML Sequence Diagram The sequence diagram is having four objects (Customer, Order, SpecialOrder and NormalOrder).

The following diagram (shown in figure 24) has shown the message sequence for SpecialOrder object and the same can be used in case of NormalOrder object. Now it is important to understand the time sequence of message flows. The message flow is nothing but a method call of an object.

The first call is sendOrder ( ) which is a method of Order object. The next call is confirm ( ) which is a method of SpecialOrder object and the last call is Dispatch ( ) which is a method of SpecialOrder object. So here the diagram is mainly describing the method calls from one object to another and this is also the actual scenario when the system is running.

Figure 25.Sequence Diagram14. UML Collaboration DiagramThe second interaction diagram is collaboration diagram. It shows the object organization as shown below. Here in collaboration diagram the method call sequence is indicated by some numbering technique as shown below. The number indicates how the methods are called one after another. We have taken the same order management system to describe the collaboration diagram.

The method calls are similar to that of a sequence diagram. But the difference is that the sequence diagram does not describe the object



organization whereas the collaboration diagram shows the object organization.

Now to choose between these two diagrams the main emphasis is given on the type of requirement. If the time sequence is important then sequence diagram is used and if organization is required then collaboration diagram is used.

Figure 26.Collaboration Diagram

15. UML Statechart Diagram The name of the diagram itself clarifies the purpose of the diagram and other details. It describes different states of a component in a system. The states are specific to a component/object of a system. A Statechart diagram describes a state machine.

Activity diagram explained in next chapter is a special kind of a Statechart diagram. As Statechart diagram defines states it is used to model lifetime of an object.

PurposeStatechart diagram is one of the five UML diagrams used to model dynamic nature of a system. They define different states of an object during its lifetime. And these states are changed by events. So Statechart diagrams are useful to model reactive systems. Reactive systems can be defined as a system that responds to external or internal events.



Statechart diagram describes the flow of control from one state to another state. States are defined as a condition in which an object exists and it changes when some event is triggered. So the most important purpose of Statechart diagram is to model life time of an object from creation to termination. Following are the main purposes of using Statechart diagrams:

To model dynamic aspect of a system. To model life time of a reactive system. To describe different states of an object during its life time. Define a state machine to model states of an object.

How to draw Statechart Diagram? Statechart diagram is used to describe the states of different objects in its life cycle. So the emphasis is given on the state changes upon some internal or external events.

Statechart diagrams are very important for describing the states. States can be identified as the condition of objects when a particular event occurs. Before drawing a Statechart diagram we must have clarified the following points:

Identify important objects to be analyzed. Identify the states. Identify the events.

The following is an example of a Statechart diagram where the state of Order object is analyzed shown in figure 27. The first state is an idle state from where the process starts. The next states are arrived for events like send request, confirm request, and dispatch order. These events are responsible for state changes of order object.

During the life cycle of an object (here order object) it goes through the following states and there may be some abnormal exists also. This abnormal exit may occur due to some problem in the system. When the entire life cycle is complete it is considered as the complete transaction as mentioned below.



Figure 27.Statechart Diagram16. UML Activity Diagram Activity diagram is another important diagram in UML to describe dynamic aspects of the system.

Activity diagram is basically a flow chart to represent the flow form one activity to another activity. The activity can be described as an operation of the system. So the control flow is drawn from one operation to another. This flow can be sequential, branched or concurrent. Activity diagrams deals with all type of flow control by using different elements like fork, join etc.

Purpose The basic purposes of activity diagrams are similar to other four diagrams. It captures the dynamic behaviour of the system. Other four diagrams are used to show the message flow from one object to another but activity diagram is used to show message flow from one activity to another.

Activity is a particular operation of the system. Activity diagrams are not only used for visualizing dynamic nature of a system but they are also used to construct the executable system by using forward and reverse engineering techniques. The only missing thing in activity diagram is the message part.

It does not show any message flow from one activity to another. Activity diagram is some time considered as the flow chart. Although the diagrams looks like a flow chart but it is not. It shows different flow like parallel, branched, concurrent and single. So the purposes can be described as:



Draw the activity flow of a system. Describe the sequence from one activity to another. Describe the parallel, branched and concurrent flow of the system.

How to draw Activity Diagram? Activity diagrams are mainly used as a flow chart consists of activities performed by the system. But activity diagram are not exactly a flow chart as they have some additional capabilities. These additional capabilities include branching, parallel flow, swimlane etc.

Before drawing an activity diagram we must have a clear understanding about the elements used in activity diagram. The main element of an activity diagram is the activity itself. An activity is a function performed by the system. After identifying the activities we need to understand how they are associated with constraints and conditions. So before drawing an activity diagram we should identify the following elements:

Activities Association Conditions Constraints

Once the above mentioned parameters are identified we need to make a mental layout of the entire flow. This mental layout is then transformed into an activity diagram.

The following is an example of an activity diagram for order management system. In the diagram shown in figure 28; four activities are identified which are associated with conditions. One important point should be clearly understood that an activity diagram cannot be exactly matched with the code. The activity diagram is made to understand the flow of activities and mainly used by the business users. The following diagram is drawn with the four main activities:

Send order by the customer Receipt of the order Confirm order Dispatch order

After receiving the order request condition checks are performed to check if it is normal or special order. After the type of order is identified dispatch activity is performed and that is marked as the termination of the process.



Figure 28.Activity Diagram

ALGORITHM / PROCEDURE / FLOWCHART: NAEXPERIMENTAL KIT: (PICTURE IF ANY) : NAPROGRAM / PSEUDO-CODE/DIAGRAM: NA

Figure 29.Collaboration Diagram



CONCLUSION / RESULT:In this Experiment, we have Study about UML (Unified Modeling Language) in brief


Batch -





Overall Marks [5] ----------------


TITLE: Developing Library Management System (Library Management Software) using Classical Life Cycle model.

PREREQUISITE: Nil


1 Processor 1.5GHz or more2 RAM 4Gb Minimum3 HDD Minimum 30Gb free Space4 Standard I/O devices


1 Operating System Windows 7 or later2 Rational Rose Enterprise

Edition 7.0 or later

THEORY:Part I: Analysis and Process framework

1. Process Model



There are six types of process models are available such as Waterfall model, prototyping model, RAD model, Incremental model, Spiral model, 4GT model. The most useful software engineering paradigm that we in co-operate in developing our project is the “Waterfall Model”. In prototyping model Prototype is built which is used for refining requirement related to software development. RAD is linear sequential software development process rapidly generally used for business levels. In Incremental model it takes the element from linear sequential model. Process is related in each increment, until complete product is produced. Spiral model is divided into number of framework activities also called regions. Software development environment that support 4GT paradigm include following tools: non procedural language for database query, report generation, high level graphics capability and spreadsheet capability but for the high level objects. But for our System Waterfall model is appropriate because of the following reasons,

1. It is linear sequential model is the oldest and the most widely used paradigm for the software engineering.

2. This approach is easy to implement because it is simplest among the process model.

3. Code generation using some program language like C, CPP, Java etc., and Take details from design phase.

4. It focuses on changes.5. The target of this process model is that a complete system will developed

after the number of refinements.6. This approach to software development begins at the system level and

progresses towards through analysis, design, coding, testing and support.7. Using this process model, implementation is get easy.

2. Common Process Framework

A1: Communication between customer and developers A2: Estimation A3: Creation of Software Scope . . .

D1: Estimation D2: Scheduling

D3: Tracking . . .


CommunicationA1A2A3A4A5A6

PlanningD1D2D3D4D5D6


M1: Analysis M2: Design

. . . .

C1: Coding C2: testing .

. . .

D1: Delivery D2: Support D3: Feedback .

. .

3. Problem Statement

Design the software to support a computerized Library management system. Each Library system provides its own computer to maintain book record and all details of student regarding to his/her books detail, his/her personal details including name, address, phone no. and all documents.

4. Cost Estimation

We do the Cost Estimation using COCOMO (COnstructive COst MOdel)Type an bn cb db

Organic 2.4 1.05 2.5 0.38

Efforts Required = E =ab(KLOC)bb

=2.4*(30)1.05

=85 PM


ModelingM1M2M3M4M5

ConstructionC1C2C3C4C5C6

Deployment

D1D2D3D4D5D6


Duration= D =Cb(E)db

=2.5*(85)0.38

=13 Months

Peoples required=E/D =85/13 =7

Efforts Required=85 PMDuration=13 MonthsPeoples required=7

PART II: SRS Contents1. Purpose of System

In project Library management system there is different facility provided that is books, newspapers, Magazines, questions paper and journals. Different people interacting with library are services provided as well as facilities user diagram gives brief idea about functioning.

2. Benefits to the End User1. They are student and staff member’s facilities provided by the system. 2. If book require is not available be suggest another reference books for only reading in library. 3. Facilities are provided to staff members are similar to those provided to students. There are

3. Disadvantages of Existing System1. Time required is very large because of manual system.2. It is get more complicated due to paper work and more tasks.3. Need to maintain catalogue.4. Paper work extended many transition token.5. Less secure.6. All Functions was not performed by Software.4. Project Specifications

Basic objective is to extends their reach to geographically scattered Students, reducing time in activities, centralized data handling and paperless issuing books, with Reduced manpower, cost cutting, operational efficiency



5. Functional Requirements

Access library database, issue book, submit book, take fine, search for book, Maintain library database, display list of all available books.

6. Proposed System

Computerized library system proposes maintaining records of book. This system does not includes

1. Finding book from rack. 2. Check its condition/finding a page.

Advantages of proposed system

1. Maintain catalog. 2. Paper work is reduced. 3. All calculations are performed by software. 4. Locating book is easy. 5. Burden on staff is reduced.

Disadvantages of Existing System

1. Large paper work is requiring for maintaining each and every record. 2. Calculations of fine also become very tedious. 3. Time required is very large because of manual system for maintaining

record. 4. If librarian and student both do not know required book then scanning

process becomes very complicated and time consuming.

7. Services

1. Book issue/renew/return. 2. Calculating time 3. Generation of daily or monthly report

8. System requirements8.1 Hardware requirements

Processor: Pentium III or aboveR. C. Patel Institute of Technology, Shirpur


RAM: 64 MB or aboveHard disk: minimum 20 GBProcessor speed: 512 MHZ

8.2 Software requirementsOperating System for developing: Windows XP, Linux Operating System Environment: Windows 98/XPTool used for developing: Java SE 89. Performance Criteria

1. While accessing records of particular category, list of books should be displayed within a second. 2. Entering data to calculated fine should be accurate.

PART III: Coding / Testing / Maintenance1. Coding

Programming or coding is next phase when system design is complete from design to code development. Now choose Java as front end because following features:

1. Easy to use. 2. Implementation is easy. 3. Updating can be easily done. 4. User friendly.

Choose back end as MS-access with following features 1. Can store large amount data.2. Table size is 64KB which is much more store. 3. Access gives user friendly to access data easily and conveniently.

2. Testing

1. After coding, testing of code generated status various system testing methods from unit testing to integration are used to in this phase.

2. Testing is used to check errors, bugs or required output.3. After coding, testing of code generated status various system testing

methods from unit. Testing to integration is used in this phase.4. Testing is used to check error, bugs or required output.

3. Maintenance/Support



It is the last phase of life cycle when system is implemented at user site. Changes are required as new platform or peripheral devices are changed. Changes may occur due to external environment.

Correction: - In this uncover logical errors are corrected. E.g. Book I.D. Data type Number but customer use character every time, so software gives error. This error can be corrected by changing data type to number.

Adaptation: - In this modification in software is done to according changes with external environment. Enhancement: - Changes because of the additional functionality requested by the customer.

Prevention: - Suppose after delivery of software customer recognize that response time of software is slow. He tells to developer to make changes in software so developers suggest recognizing software than changes.



ALGORITHM / PROCEDURE / FLOWCHART:1. Open Rational Rose Enterprise Edition 2. Select Appropriate Language For Mapping of Design

3. Select Appropriate View for New Diagram

4. Browse The Diagram To Draw From Menu.



5. Select Appropriate Diagram from the View

6. Give Appropriate Name By Renaming The File.

7. Drag & Drop the UML Building Block as Per Diagram from Tool Bar into the Workspace



8. Save Diagram at Selected Location with .Mdl Extension

EXPERIMENTAL KIT: (PICTURE IF ANY)PROGRAM / PSEUDO-CODE/DIAGRAM:



Figure 1: Activity Diagram for Library Management System

CONCLUSION / RESULT:In this Experiment, we have Design and Develop Library Management System using Classical Life Cycle model.




Batch -

Date of Experiment: __________ Date of Submission: __________


Overall Marks [5] ----------------


TITLE: Developing University Result Management System using Classical Life Cycle model.



PREREQUISITE: NilHARDWARE CONFIGURATION / KIT:

Sr. No Hardware Configuration1 Processor 1.5GHz or more2 RAM 4Gb Minimum3 HDD Minimum 30Gb free Space4 Standard I/O devices




THEORY:

Part I: Analysis and Process framework1. Process Model

The model that is basically being followed is the WATER FALL MODEL, which states that the phases are organized in a linear order. First of all the feasibility study is done. Once that part is over the requirement analysis and project planning begins. The design starts after the requirement analysis is complete and the coding begins after the design is complete. Once the programming is completed, the testing is done. In this model the sequence of activities performed in a software development project are: -

Requirement Analysis Project Planning System design Detail design Coding Unit testing System integration & testing

Here the linear ordering of these activities is critical. End of the phase and the output of one phase is the input of other phase. The output of each phase is to be consistent with the overall requirement of the system. Some of the qualities of spiral model are also incorporated like after the people concerned with the project review completion of each of the phase the work done.



WATER FALL MODEL was being chosen because all requirements were known beforehand and the objective of our software development is the computerization/automation of an already existing manual working system.2. Common Process FrameworkTask Set:

Analysis: A1 – Requirement Analysis A2 – Information Gathering A3 – Software Scope A4 – Project Scheduling A5 – Estimation A6 – ERD A7 – DFD A8 – SRS

Design: D1 – Architectural Design D2 – Component Design D3 – Interface Design D4 – Data Design

Coding: C1 – Converting Design into Code C2 – DBMS Connectivity C3 – GUI


Common Process Framework

Analysis Design

Coding Testing

C1

C3

A1

A8

D1

D4

T1

T6


Testing: T1 – Test Plan T2 – Test Cases T3 – Unit Testing T4 – Integration Testing T5 – Alpha Testing T6 – Beta Testing

3. Problem Definition

Design the software to support a computerized University management system. Each storing and accessing the data in the form of Excel sheets and account books is a tedious work. It requires a lot of laborious work. It may often yield undesired results. Maintaining these records as piles may turn out to be a costlier task than any other of the colleges and institutions4. Cost Estimation

We do the Cost Estimation using COCOMO (constructive cost model)Type an bn cb db

Organic 2.4 1.05 2.5 0.38

Efforts Required=E=ab(KLOC)bb

=2.4*(30)1.05

=85 PMDuration=D=Cb(E)db

=2.5*(85)0.38

=13 Months

Peoples required=E/D=85/13=7


PART II: SRS Contents1. Purpose of System



Design the software to support a computerized University management system. University Management System deals with the maintenance of university, college, faculty, student information within the university. This project of UMS involved the automation of student information that can be implemented in different college management.

The project deals with retrieval of information through an INTRANET or INTERNET based campus wide portal. It collects related information from all the departments of an organization and maintains files, which are used to generate reports in various forms to measure individual and overall performance of the students.

2. Benefits to the End User

1. They are student and staff member’s facilities provided by the system. 2. Facilities are provided to staff members are similar to those provided to students. 3. Reducing time in activities.4. Centralized data handling.5. Improved the operational efficiency

3. Disadvantages of Existing System

1. Time required is very large because of manual system.2. It is get more complicated due to paper work and more tasks.3. Need to maintain catalogue.4. Paper work extended many transition token.5. Less secure.6. All Functions was performed manually.

4. Project Specifications

Basic objective is to extends their reach to geographically scattered Students, reducing time in activities, centralized data handling and paperless work, with Reduced manpower, cost cutting, operational efficiency


Access University database, issue register new students, enable student login, check result, search for student, Maintain student database, display list of all registered students.

6. Non Functional Requirements



Some Functional requirements identified is listed below: The database shall be able to accommodate a minimum of 10,000 records of

students. The software shall support use of multiple users at a time.

7. Proposed System

Computerized system proposes maintaining records of colleges, students and faculty. This system does not includes

Finding records from rack. Check its condition/finding a page.

Advantages of proposed system 1. Maintain catalogue. 2. Paper work is reduced. 3. All processing is performed by software. 4. Locating records is easy. 5. Burden on staff is reduced.

Disadvantages of Existing System1. Large paper work is requiring for maintaining each and every record. 2. Time required is very large because of manual system for maintaining

record.

8. Services

1. Registering new students, colleges and courses.2. Manage large number of student details.3. Manage all details of student who registered for the course and send

appropriate details about the course to the students account.4. Create student accounts and maintain the data’s effectively.5. Generation of daily or monthly or semester report.6. Creating department, allocating courses to departments, creating faculties,

students and allocating subjects to faculties, and modifications in the data entered by the user

9. System requirements

9.1 Hardware requirements



Processor: Pentium IV or aboveRAM: 256 MB or aboveHard disk: minimum 20 GBProcessor speed: 512 MHZ

9.2Software requirements

Operating System for developing: Windows XPOperating System Environment: Windows 98/XPTool used for developing: Java SE 8

10. Performance Criteria

1. While accessing records of particular category, list of values should be displayed within a second. 2. The software should be stable in order to handle large amount of data.

11. Use case Description

Level of Use Case Description UC* Brief description Summary of what system does in response to actor’s actions UC Intermediate description Shows steps in use case, if-then UC Full description Includes Brief description, expands intermediate description, shows

scenarios

Reading and Writing Use Case Descriptions Reading: Straightforward Writing: We will not use it much Useful to practice because it leads to other modeling techniques (activity

diagram, class diagram)

Writing Use Case Descriptions1. Select a use case



2. Write abbreviated full description (Use case name, Scenario (if any), Business Event, Actors, Flow of steps, Exception conditions)

3. For figuring Flow of steps, - Keep in mind general system model: Input-Processing-Output- Steps should be at nearly the same level of abstraction (each makes

nearly same progress toward use case completion)4. For figuring exception conditions, focus on if-then logic.

Use Case Description:Use case describes how the various users access the system for particular purposeActors:-

University Administrator Student Faculty Members University Database

Precondition:- There is an active network connection to system. The system should be able to provide services.

Basic Events:- Actor:-Student Login:-The user must have to login to access various services Enter ID and password:-for the security purpose the user must have to enter

User ID and password. View Attendance:-The Student can view his college attendance report. View Result: - The student can view his academic result.

Actor:-University AdminThe University Admin Creates Courses, Create Colleges and Generates

various reports Actor:-Faculty

The Faculty members can view assigned Subjects, give marks

12. User Specification

1) Student: This class of user will use the system to fill various forms & information. Since the users will be requesting for info in the field relate to system, they will have a basic knowledge and experience with various web based applications since filling the forms does not require much technical expertise it will very easy for this class of user to use the system.



2) Faculty members: They will have a good knowledge of computer system and also the operating environment in which these systems are working in development. In order to use the system, the faculty members should be familiar with various form processes.

3) University Admin: The system administrator will be one of the university member who should be familiar with the University structure and functioning of the university she/he must also be very well familiar with all the process in the University.

There are a number of attributes of software that can serve as user specification. 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 alphabet.

PART III: Coding/Testing / Deployment/Maintenance

1. Coding




MENTION LANGUAGE U R USING

2. Testing

1. After coding, testing of code generated status various system testing



methods from unit testing to integration are used to in this phase. 2. Testing is used to check errors, bugs or required output.3. After coding, testing of code generated status various system testing


3. Deployment

1. Actual installation of product on customer site2. Description of deployment diagram.


It is the last phase of life cycle when system is implemented at user site. Changes are required as new platform or peripheral devices are changed. Changes may occur due to external environment.

Correction: - In this uncover logical errors are corrected. E.g. Book I.D. Datatype Number but customer use character every time, so software gives error. This error can be corrected by changing data type to number.

Adaptation: - In this modification in software is done to according changes with external environment.

Enhancement: - Changes because of the additional functionality requested by the customer.

Prevention: - Suppose after delivery of software customer recognize that response time of software is slow. He tells to developer to make changes in software so developers suggest recognizing software than changes.

ALGORITHM / PROCEDURE / FLOWCHART:1. Open Rational Rose Enterprise Edition.2. Select Appropriate Language For Mapping of Design



Figure 1. Use case Diagram for University Result Management System.

CONCLUSION / RESULT:In this Experiment, we have Design University Result Management System using Classical Life Cycle model.




Batch -


Title: ___________________________________________________________Evaluation 1) Attendance [2] ----------------2) Lab Performance [2] ----------------



3) Oral [1] ----------------

Overall Marks [5] ----------------


TITLE: Developing bank ATM (Automated Teller Machine) System using Classical Life Cycle model.

PREREQUISITE: NA







1. Process ModelThere are six types of process models are available such as Waterfall model, Prototyping model, RAD model, Incremental model, Spiral model, 4GT model. The most useful software engineering paradigm that we in co-operate in developing our project is the “waterfall model”. In prototyping model Prototype is built which is used for refining requirement related to software development. RAD is linear sequential software development process rapidly generally used for business levels. In Incremental model it takes the element from linear sequential model. Process is related in each increment, until complete product is produced. Spiral model is divided into number of framework activities also called regions. Software development environment



that support 4GT paradigm include following tools: non procedural language for database query, report generation, high level graphics capability and spreadsheet capability but for the high level objects. But for our System Waterfall model is appropriate because of the following reasons,


9. Requirement gathering system level and business level.10. Requirement gathering related to software.11. Code generation using some program language like C, CPP , Java etc.,

Take details from design phase.12. It’s Presentation of analysis.13. It focuses on changes.14. The target of this process model is that a complete system will

developed after the number of refinement.15. This approach to software development begins at the system level and

progresses towards through analysis, design, coding, testing and support.16. Using this process model, implementation is get easy.

2. Common Process Framework



D3: Tracking . . .


. . . .




ModelingM1M2M3M4M5



. . .


. .

3. Disadvantages of Existing System1. Time required is very large because of manual system.2. It is get more complicated due to paper work and more tasks.3. Need to maintain catalogue.4. Paper work extended many transition token.5. Less secure.6. All Functions was not performed by Software.

4. Problem StatementEach bank provides its own computer to maintain its own account and process translations, against them with the system; a client must first open account before he can use ATM. The opening account involves, the client provide his personal information, a client may open one or more account for deposit, withdraw, transfer money between checking saving account. The client can check the account status 24 hours of a day.

Our main goal is to design the s/w to support a computerized banking including customer, administrator and Automated Teller Machine. Each bank provides its own computer to maintain its customer accounts and process transaction organize them, cashier station are owned by individual banks and communication directly with their banks controller , then cashier enters account and transact data.

ATM communicates with centralized server. ATM accepts cash cards, Interact with users, communicates with central computer to carry out transaction process and print receipt multiple machine can communicates with the server. It means that user can access data through multiple ATM’s.



Deployment

D1D2D3D4D5D6


The system must handle concurrent access to the same account correctly. The bank will provide their own software for their own computer.

5. Cost Estimation

We do the Cost Estimation using COCOMO (COnstructive COst MOdel)Type An bn cb db

Organic 2.4 1.05 2.5 0.38

Efforts Required = E =ab(KLOC)bb

=2.4*(30)1.05

=85 PM

Duration= D =Cb(E)db

=2.5*(85)0.38

=13 Months

Peoples required=E/D =85/13 =7


PART II: SRS Contents1. PurposePurpose of System:-

1. The purpose of Automated Teller machine is to perform cash withdrawals and balance enquiry from anywhere in the world.

2. The hardware and software protocol describer in this document are all underactive development.

3. The function of ATM is to support a computerized banking network.

Purpose of the Document:-1. This document describes the s/w requirement and specification for on

Automated Teller Machine (ATM) network. 2. The document is intended for customer and the developer (Designers,

Testers, Maintenance’s).



Benefits of End User:- 1. Customer: An Automated Teller Machine (ATM) increases sales because it

allows customer to access all of their available cash from bank cards, credit cards etc. from almost anywhere in the world.

2. You should earn more than enough profit from surcharge fees to pay for ATM.

3. An ATM transaction is granted as eliminate charge backs, disputes, credit cards fees and bank checks.

4. It provides full services to end user.5. Maintainer: It should be easy to maintain the whole system.6. The maintainer should be the only person whom is allowed to connect a new

ATM to the network.

2. Product ScopeIn the product scope we will analyze that the user who want to use the

Automated teller machine (ATM) system would understand system or not. The Bank requested this service from a developer and customer of bank uses this system. When our ATM perform all the tasks without interruption at that time we can say that it provide good service. In early days ATM uses File system at that time some errors were occurred. But these problems are overcome by Database management System.

3. System requirement3.1 Hardware requirement

The System is required for authentication purpose. The system does not have any means of finding out, if the person using ATM card is the actual customer. So the bank issues a PIN (Personal Identification Number) to customer and asks him or her to it safe and not share with anyone else. This lets the bank assume that anyone else who knows the correct PIN (Personal Identification Number) number for an ATM card is valid customer and lets them use the ATM machine so it’s our responsibility to keep our PIN (Personal Identification Number) safe. The systems required hardware with following specifications.

Processor: Pentium III or aboveRAM: 64 MB or aboveHard disk: minimum 20 GBProcessor speed: 512 MHZ



8.2 Software requirementsOperating System for developing: Windows XP, Linux Operating System Environment: Windows 98/XPTool used for developing: Java4. Functional requirements

1. The DEC encryption protocol shall be used for communication with the bank and the ATM with a key stored internally in the device.

2. The encryption key small be set using a keypad mounted on the device.3. Three services are provided accordingly to requirement. The ATM typically

asks the user for a card and PIN (Personal Identification Number). Then customer can check the balance or withdraw money from the account.

5. Non-Functional Description1. Non-functional requirement are quality or standards for the ATM system. 2. The simple ATM allows the account holder to make deposit to and withdraw

funds.3. ATM machine by non-functional requirement.4. The ATM system under development must have or comply with but which are

not tasks that will be automated by the system.

Example:-Non-functional requirement of a system include “System must be built for a total installed cost of $1050000.00, system i.e. ATM machine must run on Windows server 2003”.The ATM system must be secured against Trojan attacks.This software development methodology helps to identify, document and realize the requirement. Non-functional requirement describe how the product should be implemented.

6. Use Case Description

Use case describes how the bank customer or account holder uses the ATM to withdraw money.Actors:-

Account holder Bank /Database

Precondition:- There is an active network connection to the bank.



The ATM has cash available.Basic Events:-

Insert card:-The account holder insert the card into the ATM machine to retrieve the amount from the bank.

Enter pin no.:-for the security purpose the amount holder must have to enter PIN.

Select amount type:-The account holder have to select the type of account so that ATM prompts for an amount.

Withdraws money: -card ID, PIN, Amount and account is sent to the bank as a transaction. The account holder withdraws a money from the account in the bank.

Transfer money: - by using this kind of transaction the account holder transfers money from or into account in the bank.

Balance enquiry:-The account holder can check or get the enquiry of the balance before the money dispensed. The bank consortium replies with go/don’t go reply telling if the transaction is ok.Maintenance:-The ATM technician is responsible for the maintenance of records in the bank of ATM system.Repair:-The ATM technician repairs the account related facilities so that they or customer or user can withdraws the data successfully. System operator:-The system operator is responsible for the system start up and system shut down purpose.

7. User specifications

In the user specification basically we focused on what are the capabilities of the user or what type of user use our system. The user should have the thorough knowledge of the system that he or she might uses. He or she knows about what system they are using. The end user is used to distinguish those who only operate the software from the developer of the system, who knows a programming language and uses it to create new function to end users. Computer systems are divided into two groups based on the kind of user they have,1. Customer: - The customer interacts with ATM network via ATM. It must be easy for them to use ATM. They should be supported by the system in every possible way.



2. Maintainer: - It should be easy to maintain the whole system. The maintainer should be the only person that is allowed to connect a new ATM to the network.

8. Proposed System

In our system, the automated teller machine after inserting the card it will asks password to us. After a valid password it will asks an account type then user would have to select account i.e., it is current or saving. After selecting account then user would have to choose option for withdrawal, PIN change etc. After collecting amount it will asks for a receipt. After processing yes we got a receipt of a corrected transaction.

9. Services 4. Checking of an Automated Teller Machine (ATM) ID is correct or not.5. It provides cash withdrawal after checking account type.6. It provides current updating of process.7. Online banking services8. Mobile banking services9. Online payment10. It also provides security to account with ID and password etc.11. PIN (Personal Identification Number) change.

10. Data dictionary

1. PIN: PIN is nothing the Personal Identification Number. It is unique for the every account holder. It is provided by the bank for the customized user of the bank. It is just like a password to your account. After inserting the correct PIN number user can proceeds to their respective account transactions.

2. Account: After inserting the correct PIN, the system asks for the type of account such that it is current or saving account. According to your account type respective operations or transactions can be performed on your account.

3. Transaction: Which type of transaction the user would have to do such that he/she can change the PIN (Personal Identification Number) as well as they can withdrawal of a money. Also they can check the balance in the account as well as one can transfer the cash within accounts.



4. Receipts: After the corrected transaction the machine or system would ask a user did he want the receipt or not. If he presses yes key then he gets the receipt otherwise not.

5. CANCEL key: There will be the cancel key on your system. If someone press wrong PIN or ID and after sometimes he /she recognize that it is incorrect then after pressing CANCEL key you can cancel your corresponding transaction.

6. CLEAR key: After the whole complete transaction the user can press clear key, by pressing this key user can refresh the machine.





2. Testing




3. Maintenance/SupportIt is last phase of life cycle when system is implemented at user wants



changes are required as new platform with OS May peripheral devices are changes.

1. Correction: - In this uncover logical errors are corrected. E.g. Pin code data type Number but customer use character every time, so software gives error. This error can be corrected by changing data type to number.

2. Adaptation: - In this modification in software is done to according changes with external environment. Modification in software is done according changes with environment.

3. Enhancement: - Changes because of the additional functionality requested by the customer. Customer required some additional functions at that time in enhancement is done in the software or product.

4. Prevention: - Suppose after delivery of software customer recognize that response time of software is slow. He tells to developer to make changes in software so developers suggest recognizing software than change.

4. Advantages of the Implemented System

1. ATM management system is an automated machine used to withdraw the money anywhere the branch or ATM of that bank is present.

2. Also the other functionality which ATM provides it makes the life of customer easier by saving the time of customer to go in the bank.

3. ATM management system can be used by day by day process.4. It saves the time and we can withdraw money into few seconds.5. Round the clock Services:-ATM provides banking services to its customers

round the clock 24 hours a day, 7 days a week and 365 days a year.6. Access to the bank from any part of the world:-Essential banking services

like deposits, withdrawals, transfer of funds from any part of the world is possible due to ATM.

7. Expansion of services to any corner of the world:-The banks can expand their services to any corner of the world by providing electronics access to their customers.

8. Reduction of cost operation:-This reduces human iteration and thereby reduces the cost operations and increase profitability of banks.

ALGORITHM / PROCEDURE / FLOWCHART:1. Open Rational Rose Enterprise Edition.



2. Select Appropriate Language For Mapping of Design





Figure 1: Activity Diagram for ATM System.

CONCLUSION / RESULT:In this Experiment, we have Design and Develop bank ATM (Automated Teller Machine) System using Classical Life Cycle model.




Batch -



Overall Marks [5] ----------------

Subject Incharge

Experiment No.5TITLE: Developing Hospital Management System using Classical Life Cycle model.



PREREQUISITE: NA






THEORY:

Part I: Analysis and Process framework1. Process ModelThere are six types of process models are available such as Waterfall model, Prototyping model, RAD model, Incremental model, Spiral model, 4GT model. The most useful software engineering paradigm that we in co-operate in developing our project is the “waterfall model”. In prototyping model Prototype is built which is used for refining requirement related to software development. RAD is linear sequential software development process rapidly generally used for business levels. In Incremental model it takes the element from linear sequential model. Process is related in each increment, until complete product is produced. Spiral model is divided into number of framework activities also called regions. Software development environment that support 4GT paradigm include following tools: non procedural language for database query, report generation, high level graphics capability and spreadsheet capability but for the high level objects. But for our System Waterfall model is appropriate because of the following reasons,


2. Requirement gathering system level and business level.3. Requirement gathering related to software.4. Code generation using some program language like C, CPP, Java etc., and

Take details from design phase.5. It’s Presentation of analysis.6. It focuses on changes.



7. The target of this process model is that a complete system will developed after the number of refinement.

8. This approach to software development begins at the system level and progresses towards through analysis, design, coding, testing and support.

9. Using this process model, implementation is get easy.2. Common Process Framework



D3: Tracking . . .


. . . .


. . .


. .




ModelingM1M2M3M4M5


Deployment

D1D2D3D4D5D6


4. Problem StatementProblems with conventional system1. Lack of immediate retrievals: -The information is very difficult to retrieve and to find particular information like- E.g. - To find out about the patient’s history, the user has to go through various registers. This results in inconvenience and wastage of time.2. Lack of immediate information storage: - The information generated by various transactions takes time and efforts to be stored at right place.3. Lack of prompt updating: - Various changes to information like patient details or immunization details of child are difficult to make as paper work is involved.4. Error prone manual calculation: - Manual calculations are error prone and take a lot of time this may result in incorrect information for example calculation of patient’s bill based on various treatments.5. Preparation of accurate and prompt reports: - This becomes a difficult task as information is difficult to collect from various registers.

5. Cost Estimation

According to Inventory management system we are move towards to “Organic” mode. So in this organic mode the project size typically 2-50 KLOC. As our observation the inventory management system is a small size project, experience developers in the familiar environment. It development environment is familiar & in house. So, according to the observations we assume some figures. Suppose that a project was estimated to be 400 LOC.

Project ab bb Cb db

Organic 2.4 1.05 2.5 0.38Semidetached

3.0 1.12 2.5 0.35

Embedded 3.6 1.20 2.5 0.32

The basic COCOMO equations take the formE= ab (LOC)bb D= cb (LOC)db

Organic mode E = 2.4(400)1.05 = 1295.31 PM



D = 2.5(1295.31)0.38 = 38.07 M

According to figure as shown above E = is effort applied in person-monthsD= is the development time in monthsAvg. staff size (SS) = E/D persons.1295.31/38.07 = 34 approx.

PART II: SRS Contents1. PurposePurpose of System:-The purpose of the system is to support a computerized system for patient & doctor. Each hospital system provides a computer to each of them for hospital management & process to organize them. In this, Patient wants to Log in the system. Check up and Fill all information related with patient, whenever doctors want to log in the system. Record for patient id & the time for meeting the doctor are made in computer. Also Enquiry Counter will check the number of recipients. Accurate calculations should be made.

3. System requirement3.1 Hardware requirement

Processor: Pentium III or aboveRAM: 256 MB or aboveHard disk: minimum 20 GB or moreProcessor speed: 512 MHZ

8.2 Software requirementsOperating System for developing: Windows XP, Linux Operating System Environment: Windows 98/XPTool used for developing: Visual Studio .Net Version: 2003 for coding Back-end database: Microsoft SQL Server Version: 2000


A Hospital is a place where Patients come up for general diseases. Hospitals provide facilities like:-

1. Consultation by Doctors on Diseases.2. Diagnosis for diseases.3. Providing treatment facility.



4. Facility for admitting Patients (providing beds, nursing, medicines etc.)5. Immunization for Patients/Children.

Various operational works that are done in a Hospital are:-1. Recording information about the Patients that come.2. Generating bills.3. Recording information related to diagnosis given to Patients.4. Keeping record of the Immunization provided to children/patients.5. Keeping information about various diseases and medicines available to cure

them.

These are the various jobs that need to be done in a Hospital by the operational staff and Doctors. All these works are done on papers. The work is done as follows:-

1. Information about Patients is done by just writing the Patients name, age and gender. Whenever the Patient comes up his information is stored freshly.

2. Bills are generated by recording price for each facility provided to Patient on a separate sheet and at last they all are summed up.

3. Diagnosis information to patients is generally recorded on the document, which contains Patient information. It is destroyed after some time period to decrease the paper load in the office.

4. Immunization records of children are maintained in pre-formatted sheets, which are kept in a file.

5. Information about various diseases is not kept as any document. Doctors themselves do this job by remembering various medicines.

All this work is done manually by the receptionist and other operational staff and lot of papers are needed to be handled and taken care of. Doctors have to remember various medicines available for diagnosis and sometimes miss better alternatives as they can’t remember them at that time.

7. User Specifications

1. Patients:-Number of patients coming hospital having number of several of decease. The patient has to go inquiry office and give his/her whole details and which type of disease he/she suffering from. Every patient must have register themselves and pay the initial registration fee to the inquiry office whatever the charges the hospital has decided. After the patient is registered according to his/her status whether he is new or old patient she/he is diverted to consult or doctor specialist.



2. Inquiry office:-This department is the public interface to the hospital. A new or old patient visiting doctors, specialist etc. So inquiry office will take the information from patient and guide him/her that to whom they should contact.

3. Doctors: Doctors are the important part of this management system. Doctors checks the patient and diagnose the problem and then they will be admitted the patient otherwise they will be giving medicines to the patients.

4. Staff: There are many people working in the staff like nurses and work boys. They give medicines to indoor patients and take care of patients.

User CharacteristicsEvery user should be:• Comfortable of working with computer.• He must have knowledge in medical field.• He must also have basic knowledge of English too.

8. Proposed System

1. The project maintains two levels of users:-• Administrator Level-Doctor• User Level-Data Entry Operator

2. In this project collection of data is from different pathology labs.3. Results of tests, prescription, precautions and diet advice will be

automatically updated in the database.4. Related test reports, patient details report, prescription and billing reports

can be generated as per user requirements.5. User or Administrator can search a patient’s record by his/her name or their

registration date.6. Patient’s diet advice can be provided in Hindi.

9. Services

1. Maintaining records of indoor/outdoor patients.2. Maintaining patients diagnosis details, advised tests to be done.3. Providing different test facilities to a doctor for diagnosis of patients.a. X-Ray



b. Urine Testc. Stool Testd. Sonography Teste. Gastroscopy Testf. Colonoscopy Testg. Blood Testh. Biochemistry Test4. Maintaining patient’s injection entry records.5. Maintaining patient’s prescription, medicine and diet advice details.6. Providing billing details for indoor/outdoor patients.7. Maintaining backup of data as per user requirements (between mentioned

dates).8. If user forgets his/her password then it can be retrieved by hint question.


Programming or coding is next phase when system design is complete from design to code development.

Advantages of Visual Studio .Net Version: 2003 Framework1. NET is the framework for which we develop applications. It sits in between

our application programs and operating system. Applications developed for .NET run inside .NET and are controlled by .NET. It supports both Windows and web applications.

2. NET provides an object oriented environment. It ensures safe execution of the code by performing required runtime validations. For example, it is never possible to access an element of an array outside the boundary. Similarly, it is not possible to a program to write into another programs area, etc. The runtime validations performed by .NET makes the entire environment robust.Now choose SQL Server 2000 as back end because following features:

9. The SQL Server 2000 database engine includes integrated XML support.10. Scalability and Availability: The same database engine can be used

across platforms ranging from laptop computers running Microsoft Windows® 98 through large, multiprocessor servers running Microsoft Windows 2000 Data Center Edition.

11. Ease of installation, deployment, and use.

2. Testing






3. Maintenance/SupportIt is last phase of life cycle when system is implemented at user wants changes are required as new platform with OS May peripheral devices are changes.

5. Correction: - In this uncover logical errors are corrected. E.g. Patient ID data type Number but customer use character every time, so software gives error. This error can be corrected by changing data type to number.

6. Adaptation: - In this modification in software is done to according changes with external environment. Modification in software is done according changes with environment.

7. Enhancement: - Changes because of the additional functionality requested by the customer. Customer required some additional functions at that time in enhancement is done in the software or product.

8. Prevention: - Suppose after delivery of software customer recognize that response time of software is slow. He tells to developer to make changes in software so developers suggest recognizing software than change.

ALGORITHM / PROCEDURE / FLOWCHART:1. Open Rational Rose Enterprise Edition 2. Select Appropriate Language For Mapping of Design



Figure 1: Class Diagram for Hospital Management System.

CONCLUSION / RESULT:In this Experiment, we have Design and Developing Hospital Management System using Classical Life Cycle model.




Batch -



Overall Marks [5] ----------------

Subject Incharge

Experiment No.6TITLE: Developing College Admission System using Classical Life Cycle model.



PREREQUISITE: NA







1. Process ModelHere we use Waterfall Model; Waterfall Model is useful for the project in which the requirement are well understood and uniquely to change radically during the system development.

It is the oldest software paradigm. This model suggests a systematic, sequential approach to software development. The software development starts with requirements gathering phase. Then progress through analysis, design, coding, testing and maintenance.

2. Common Process FrameworkTask Set:



Analysis: A1 – Requirement Analysis A2 – Information Gathering A3 – Software Scope A4 – Project Scheduling A5 – Estimation A6 – ERD A7 – DFD A8 – SRS

Design: D1 – Architectural Design D2 – Component Design D3 – Interface Design D4 – Data Design

Coding: C1 – Converting Design into Code C2 – DBMS Connectivity C3 – GUI

Testing: T1 – Test Plan T2 – Test Cases T3 – Unit Testing T4 – Integration Testing


Common Process Framework

Analysis Design

Coding Testing

C1

C3

A1

A8

D1

D4

T1

T6


T5 – Alpha Testing T6 – Beta Testing

3. Problem StatementSince the management of data is not an online system, therefore it has difficult in integrating the data. If the teachers, students or parents require any information, they must contact the administrator.

Information about course, such as professor, department and prerequisites, will be included to help student make informed decision.

At the end of semester, the student will be able to access the system to view an electronic report card. Since student grades are sensitive information. The system must be notified of the change before submitting the schedule for processing.

This system develops is to resolve the problem become from manual system

Data losses Counting errors Data redundancies No database to store information No backup & security

4. Cost Estimation

Effort:E = ab(KLOC)bb

E = 2.4(10)1.05

E = 26.92 ≈ 27E = 27pm

We require Efforts at least 27 per month

Duration:D = cb(E)db

D = 2.5(27)1.05

D = 8.74 ≈ 9mWe require Duration at least 9 month

People:P = E/DP = 27/9P = 3

We require at least 3 People



Part – II: SRS Contents

1. Purpose

General Purpose:Student Admission System supports the student admission and

registration process, the maintenance of student personal, academic and its fee related data.

Database maintained by this system usually contains the student’s personal, academic and its fee related information. It focuses on storing & processing (insertion, updation).

Purpose of Document:The purpose of this document is to describe the student registration

system which will be used to automate the student registration process & other forms that the student submits for a particular request.

This application’s overall purpose is to make the student admission process easier & also help manage programs offered by department more efficiently.

This document defines & describes the operations interfaces, performance & quality assurance requirement of student registration system.

Customer Benefits:Here in this system college is customer so by using this system college

stored information in easy way & reduce the time, cost & manpower.

User Benefits:Here in this system; students, teachers, parents are user so easy to get

academic report & information, easy to get personal information, easy to get fees related data & information.

2. Disadvantage of Existing System1. It is tedious work to maintain handwritten records.2. Possibility of losing data.3. Possibility of misplacing of file in which all records are stored.4. All the work at the time of admission of the students is done manually by ink

and paper, which is very slow and consuming much efforts and time.



5. Require much man power i.e. man efforts, much cost & hard to operate and maintain.

6. Since, all the work is done in papers so it is very hard to locate a particular student record when it is required.

3. Proposed SystemDesign the software to support a computerized student admission system. Each admission system provides its own computer to maintain student information and all details of student regarding to his/her marks detail his/her personal details including name, address, phone no. and all documents.

Basic object are to extend their system to reach geographically scattered students, reducing time in activities, centralized data handling and paperless admission with reduced manpower. Cost cutting, operational efficiency consists of view of data and integration with other factors. Main challenges are effectively synchronized internal and external operation in such a manner that job can be finished within time to limit and integration with different agencies on an agreed upon common data format.

4. Services1. Check for student id and password.2. Provide admission form to fill.3. Provide scholarship form to fill.4. Provide university form to fill.

5. ScopeThis software/system maintain database of student then user can access data for many purposes like as academic, personal, fees etc. details.

Activities like updation 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 system.Information Objectives:

Academic detail Personal detail Fees detail Tables of above all points

Function & Performance: Generate Academic report Generate Personal report



Generate Fees report

6. System Requirement

a) Software Environment Microsoft Project Rational Rose PHP web language, C language

b) Operating System/Server One set of personal computer with windows XP/7/8 platform Apache as a server

c) Database System MY SQL

d) Hardware requirement RAM – 256 MB Hard Disk – 40 GB CPU – 1.70 MHZ

e) Network requirement LAN (Local Area Network)

7. Functional Requirement

It performs various functions one of them is filling forms. The student will interact to student admission system with login password and ID. The student system will verify student ID & password and if entered ID verification is successful then system allows for filling admission form.

8. Non Functional Requirement

1) The machine i.e. student admission system have to maintain all student information and student details.

2) When student login information system, the machine should check ID and password with perspective student.

9. Use Cases

1) Login2) Filling Form3) Submitting Documents



4) Paying Fees5) Report Generation

10. User Specification

1. Student: This class of user will use the system to fill various forms & place requests. Since the users will be applying for higher studies in the field relate to computer, they will have a basic knowledge and experience with various web based applications since filling the forms does not require much technical expertise it will very easy for this class of user to use the system.

2. Faculty members/Department co-ordinators: They will have a good knowledge of computer system and also the operating environment in which these systems are working in development. In order to use the system, the faculty members should be familiar with various form processes.

3. System Co-ordinator: The system administrator will be one of the department member should be familiar with the department structure and functioning of the department She/he must also be very well familiar with all the process in the department.

PART III: Coding / Testing / Maintenance

1. Data DictionaryStudent:

STUD_NAME:STRING – Name of the student with data type String STUD_ID:INT - ID of the Student with data type Integer LOGIN( ) – It is a function which gives login form VIEW_RESULT( ) - It is a function which gives Result Sheet

Professor: PROF_NAME:STRING - Name of the student with data type String STUD_ID:INT - ID of the Student with data type Integer FILL_RESULT( ) - It is a function which gives fill Result Sheet

Course Catalog Database: FILL_Grades( ) - It is a function which gives fill Grade Sheet

Billing System: PROVIDE_BILL - It is a function which gives Billing Information

Report Card:



DISPLAY_RESULT - It is a function which gives Mark sheet

2. Coding

Programming or coding is next phase when system design is complete from design to code development. Now choose VB 6.0 as front end because following features:

Easy to use. Implementation is easy. Updation can be easily done. Cost designing software using VB is less. User friendly.

Choose back end as MS-access with following features:

Can store large amount data Table size is 64KB which is much more store. Access gives user friendly to access data easily and conveniently.

3. Testing

Once code has been generated, program testing begins. The testing process focuses on the logical internals of the software, ensuring that all statements have been tested, and on the functional externals; that is, conducting tests to uncover errors and ensure that defined input will produce actual results that agree with required results.

Software testing is an empirical technical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate.

An important point is that software testing should be distinguished from the separate discipline of Software Quality Assurance (S.Q.A.), which encompasses all business process areas, not just testing.

4. Deployment

Here in this system following elements of deployment1. Server – Course Catalogue Database2. Switch – one switch is used3. Cable – CAT 5 cable is used



4. Client – Three Clients are used i.e. CLIENT1 SRS, CLIENT2 SRS, CLIENT3 SRS


It is last phase of life cycle when system is implemented at user wants changes are required as new platform with OS May peripheral devices are changes.

Correction: In this uncover logical errors are corrected. E.g. Bookid data type number but customer use character every time, so software gives error. This error can be corrected by changing data type to number.

Adaptation: In this modification in software is done to according changes with external environment.

Enhancement: Changes because of the additional functionality requested by the customer.

Prevention: Suppose after delivery of software customer recognize that response time of software is slow. He tells to developer to make changes in software so developers suggest recognizing software than changes.

6. Features of the Implemented System

Our School Enrollment Software tools allow you to easily create, modify, and deploy forms to an online parent portal.

This allows you to reap the benefit of a massive cost reduction in your annual enrollment and registration process. No more paper to lose, no more trying to figure out what the parent wrote. Instead you end up with clear validated data that is ready for your student management system.

In short, you are in control your forms, your process, your way. Student Registration - First day packets have historically been a long and

rigid process. It involved creating your forms in MS Word or Adobe format; getting approval from all interested parties, making changes, and sending them off to a print shop. Corrections to any paper forms are expensive to implement and really cannot be done at the last minute.

Report Cards - Report cards can be easily generated with School Office Pro. Report cards are also customizable school and grade level.

E-Commerce - There are many things that a parent might be asked to pay for: PTA Memberships, Yearbooks, Student ID cards, Auction Tickets, AP Tests, the list goes on. Throughout the year, students bring home one order



form after another that has to be looked at, decided on, and paid for. Most parents today would rather just pay for everything up front.

Mass e-mail - One of the keys to a successful relationship is communication. Another is letting parents control exactly what communication they receive. Communicating with your parents, students, and staff has never been easier with School Office Pro Mass Email. Create groups and send emails to everyone that has signed up.

Human Resources - Potential candidates will always start at your website when trying to find an open position. We've found that our dynamic forms engine is perfect for this situation. Post jobs to your schools web sites, accept applications, and track candidates through the approval process.

Student Surveys - Sometimes you just have a simple form that needs filled out. You can create it in School Office Pro and distribute it to your parent population or even by putting a link on your website. Publish a single page form or survey directly to your website. This is an easy way to get instant feedback.

Time Tracking - Tracking student internships used to be a time consuming paper based process. With School Office Pro, you can allow students to submit time sheets for review to track internship progress.

ALGORITHM / PROCEDURE / FLOWCHART:1. Open Rational Rose Enterprise Edition 2. Select Appropriate Language for Mapping of Design





Figure 1: Use case Diagram for College Admission System.

CONCLUSION / RESULT:



In this Experiment, we have Design and Develop College Admission System using Classical Life Cycle model.
