A Project Report On

Blog website
Submitted in partial fulfilment of the requirement for the

Award of the degree of B.Sc (CS)

By

Student name

Roll no.

Under the Guidance of

MR .Teacher name (ASSIT. PROFESSOR)

Department of Computer Science

Hari Institute of Technology

Approved by

M.S University

SAHARANPUR – 247120.
 DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE

This is to certify that Student name (roll no) of the final year B.Sc(CS) have carried out a
project work on “BLOG WEBSITE” under the guidance of Assit. Teacher name
Department Of Computer Science for the partial fulfilment of the award of the degree of
B.Sc(CS) in Hari Institute of Technology, Randevi Nakur Saharanpur (Affiliated to U.P.
M.S University, SAHARANPUR) is a bonafide record of work done by them during the year
2023-24.

Head of the Department:

Signature with Date

NAME & DESIGNATION

 Acknowledgement

I take this opportunity to express my sincere thanks and deep gratitude to all those people
whoextended their wholehearted co-operation and have helped me in completing this project
successfully.

First of all Special thanks to Mr.Teacher name for all the help and guidance extended to me by
him in every stage during my training. His inspiring suggestions and timely guidance enabled me
to perceive the various aspects of the project in a new light. I would like to thank him for guiding
and encouraging me throughout the duration of the project.

I would also thank to all our faculties member and lab staff without their support this project
would have remained a dream.

At last but not the least, I give my hearty thanks to all my friends and my family members who
took great pains to boot up my morale always.

Student name
B.Sc(CS) VI SEM
Roll No. :
 CONTENTS

1. Project Detail

1.1 Introduction

1.2 Project description

1.3 Objective

2. System Development methodologies

3. Initial Investigation and System Requirements

3.1 System Study and Problem Formulation

3.2 Project Category

3.3 Platform (Technologies/Tools)

3.4 Front-end and Back-end Tools

3.5 Software and Hardware Used

4. Feasibility Study

5. System Design

5.1 Data Flow Diagrams

5.2 E-R Diagrams

5.3 Flow Chart

5.4 Data Base Design

5.5 Snap Shots

5.6 Coding

6. Testing and System Security

7. Quality Assurance

8. Implementation and maintenance

9. Evaluation

10. Conclusion

11. Bibliography
PROJECT DETAILS

 INTRODUC
TION
 DESCRIPTI
VE
 OBJECTIVE
1.1 INTRODUCTION:-
Welcome to Stand Blog, your ultimate destination for blogs , designed to inform, inspire, and
engage. Our blog is dedicated to exploring a wide array of subjects including technology,
lifestyle, education, travel, sports, finance, fashion, food, automobile, psychology etc, providing
you with insightful articles, practical tips, and thought-provoking discussions.

Our Mission

At Stand Blog we aim to:

 Inform: Deliver accurate and up-to-date information on the latest trends and
developments in technology, lifestyle, education, travel, sports, finance, fashion, food,
automobile, psychology etc,

 Inspire: Share stories and experiences that motivate our readers to pursue their passions
and dreams.

 Engage: Foster a community of like-minded individuals who can share ideas, provide
support, and grow together.

What We Offer

 Expert Insights: Our team of knowledgeable writers and guest contributors bring you
expert opinions and in-depth analyses.

 Practical Tips: From how-to guides to top lists, we provide actionable advice that you
can apply in your everyday life.
  Engaging Stories: We believe in the power of storytelling to connect and inspire. Our
blog features personal stories, interviews, and case studies that resonate with our readers.

 Interactive Community: Join the conversation through comments, social media, and
community events. Your voice matters, and we encourage active participation.

Why Choose Us?

 Quality Content: We prioritize well-researched and well-written articles that add value
to our readers.

 Diverse Perspectives: Our content reflects a variety of viewpoints, ensuring a well-

rounded and inclusive approach.

 Constant Updates: Stay ahead of the curve with regular updates on the latest trends and
insights.

Join Us

We invite you to explore our blog, engage with our content, and become a part of our growing
community. Whether you are here to learn something new, find inspiration, or connect with
others. Thank you for visiting Stand Blog. We look forward to sharing this exciting adventure
with you!

Who Needs a Blog Website?

Blog websites serve a variety of purposes and can be beneficial to a wide range of individuals
and organizations.

Here's a look at who might benefit from having a blog website and why:

1. Individuals and Personal Brands

 Writers and Journalists: A blog provides a platform to showcase writing skills, share
stories, and build a portfolio.
 Experts and Influencers: Sharing expertise and opinions helps establish authority in a
niche and connect with a wider audience.
 Job Seekers: Demonstrating knowledge and passion through a blog can make job
applications stand out.

2. Businesses and Entrepreneurs

 Startups and Small Businesses: Blogs can drive traffic to the website, improve SEO,
and convert visitors into customers by providing valuable content.
 E-commerce Stores: Content marketing through blogs can enhance product visibility,
explain usage, and build trust with potential buyers.
 Service Providers: Demonstrating expertise and sharing case studies can attract new
clients and retain existing ones.

3. Non-Profit Organizations
 Awareness Campaigns: Blogs can spread awareness about causes, share success
stories, and provide updates on initiatives.
 Engaging Donors and Volunteers: Regular content helps keep supporters informed and
engaged with the organization's mission.
 4. Educational Institutions
 Schools and Universities: Sharing news, research, and student achievements can
enhance community engagement and attract prospective students.
 Teachers and Educators: Personal or collaborative blogs can provide additional
resources, insights, and a platform for student interaction.

Who is a Blogger?

A blogger is an individual who writes and publishes content on a blog. Bloggers typically share
their insights, experiences, opinions, or expertise on various topics, such as travel, food
technology, lifestyle, fashion, and more. They use their blog as a platform to engage with an
audience, provide valuable information, and often influence their readers. Bloggers may also
monetize their blogs through advertisements, sponsored posts, affiliate marketing, and selling
products or services.

What can I expect?

From a blogger, you can typically expect:

 Regular Content Updates: Blog posts on topics of interest, which might include personal
experiences, professional advice, reviews, or tutorials.
 Engagement: Interaction with readers through comments, social media, and sometimes
live sessions.
 Unique Perspective: Personal insights and opinions that differentiate their content from
others.
 Multimedia Content: Use of images, videos, and infographics to complement written
posts.
 Expertise or Niche Focus: Deep dives into specific subjects or industries based on the
blogger's expertise or interests.
 Monetization Efforts: Sponsored posts, affiliate links, or advertisements to generate
income.
 Consistency: A regular posting schedule to keep the audience engaged.
Strengths of Blogging
Blogging has several strengths that make it a powerful medium:

 Personal Connection: Blogs allow for a personal touch, helping bloggers build a direct
and meaningful connection with their audience.
 Authority and Expertise: Regular, high-quality content can establish a blogger as an
authority in their niche.
 SEO Benefits: Well-written blog posts can improve search engine rankings, driving
more organic traffic to the site.
 Community Building: Blogs can foster a community of readers with similar interests,
encouraging interaction and engagement.
 Flexibility: Bloggers have the freedom to cover a wide range of topics and experiment
with different content formats.
 Monetization Opportunities: Successful blogs can generate revenue through ads,
sponsored posts, affiliate marketing, and selling products or services.
 Long-Term Value: Unlike social media posts, blog content has a longer lifespan and can
continue to attract readers and generate traffic over time.
 Creativity and Expression: Blogging provides a platform for creativity, allowing
individuals to express their ideas, opinions, and stories in a unique way.
 Educational Resource: Blogs can be a valuable resource for readers looking to learn
about specific topics, offering in-depth information and insights.
 Networking: Blogging can open up opportunities for networking with other bloggers,
influencers, and professionals in the industry.
Overall, blogging is a versatile and impactful medium that can serve both personal and
professional purposes.
 SYSTEM
DEVELOPMENT
METHODOLOGIES

SDLC
 SYSTEM DEVELOPMENT LIFE
CYCLE

System Development Methodology

System Development Life Cycle Phases:

1.2.1 Initiation Phase

The initiation of a system (or project) begins when a business needs or opportunity is identified.
A Project Manager should be appointed to manage the project. This business need is documented
in a Concept Proposal. After the Concept Proposal is approved, the System Concept
Development Phase begins.

1.2.2 System Concept Development Phase

Once a business need is approved, the approaches for accomplishing the concept are reviewed
for feasibility and appropriateness. The Systems Boundary Document identifies the scope of the
system and requires Senior Official approval and funding before beginning the Planning Phase.

1.2.3 Planning Phase

The concept is further developed to describe how the business will operate once the approved
system is implemented, and to assess how the system will impact employee and customer
privacy. To ensure the products and /or services provide the required capability on-time and
within budget, project resources, activities, schedules, tools, and reviews are defined.
Additionally, security certification and accreditation activities begin with the identification of
system security requirements and the completion of a high level vulnerability assessment.

1.2.4 Requirements Analysis Phase

Functional user requirements are formally defined and delineate the requirements in terms of
data, system performance, security, and maintainability requirements for the system. All
requirements are defined to a level of detail sufficient for systems design to proceed. All
requirements need to be measurable and testable and relate to the business need or opportunity
identified in the Initiation Phase.

1.2.5 Design Phase

The physical characteristics of the system are designed during this phase. The operating
environment is established, major subsystems and their inputs and outputs are defined, and
processes are allocated to resources. Everything requiring user input or approval must be
documented and reviewed by the user. The physical characteristics of the system are specified
and a detailed design is prepared. Subsystems identified during design are used to create a
detailed structure of the system. Each subsystem is partitioned into one or more design units or
modules. Detailed logic specifications are prepared for each software module.

1.2.6 Development Phase

The detailed specifications produced during the design phase are translated into hardware,
communications, and executable software. Software shall be unit tested, integrated, and retested
in a systematic manner. Hardware is assembled and tested.

1.2.7 Integration and Test Phase

The various components of the system are integrated and systematically tested. The user tests the
system to ensure that the functional requirements, as defined in the functional requirements
document, are satisfied by the developed or modified system.

Prior to installing and operating the system in a production environment, the system must
undergo certification and accreditation activities.

1.2.8 Implementation Phase

The system or system modifications are installed and made operational in a production
environment. The phase is initiated after the system has been tested and accepted by the user.
This phase continues until the system is operating in production in accordance with the defined
user requirements.
1.2.9 Operations and Maintenance Phase

The system operation is on-going. The system is monitored for continued performance in
accordance with user requirements, and needed system modifications are incorporated. The
operational system is periodically assessed through In-Process Reviews to determine how the
system can be made more efficient and effective. Operations continue as long as the system can
be effectively adapted to respond to an organization’s needs. When modifications or changes are
identified as necessary, the system may re-enter the planning phase.

1.2.10 Disposition Phase

The disposition activities ensure the orderly termination of the system and preserve the vital
information about the system so that some or all of the information may be reactivated in the
future if necessary. Particular emphasis is given to proper preservation of the data processed by
the system, so that the data is effectively migrated to another system or archived in accordance
with applicable records management regulations and policies, for potential future access.

SDLC Objectives:

This guide was developed to disseminate proven practices to system developers, project
managers, program/account analysts and system owners/users throughout the DOJ. The specific
objectives expected include the following:

 To reduce the risk of project failure

 To consider system and data requirements throughout the entire life of the system
 To identify technical and management issues early
 To disclose all life cycle costs to guide business decisions
 To foster realistic expectations of what the systems will and will not provide
 To provide information to better balance programmatic, technical, management, and cost
aspects of proposed system development or modification
 To encourage periodic evaluations to identify systems that are no longer effective
  To measure progress and status for effective corrective action
 To support effective resource management and budget planning
 To consider meeting current and future business requirements

Key Principles

This guidance document refines traditional information system life cycle management
approaches to reflect the principles outlined in the following subsections. These are the
foundations for life cycle management.

Life Cycle Management Should be used to Ensure a Structured Approach to Information

Systems Development, Maintenance, and Operation

This SDLC describes an overall structured approach to information management.

Primary emphasis is placed on the information and systems decisions to be made and the proper
timing of decisions. The manual provides a flexible framework for approaching a variety of
systems projects. The framework enables system developers, project managers, program/account
analysts, and system owners/users to combine activities, processes, and products, as appropriate,
and to select the tools and methodologies best suited to the unique needs of each project.

Support the use of an Integrated Product Team

The establishment of an Integrated Product Team (IPT) can aid in the success of a
project. An IPT is a multidisciplinary group of people who support the Project Manager in the
planning, execution, delivery and implementation of life cycle decisions for the project. The IPT
is composed of qualified empowered individuals from all appropriate functional disciplines that
have a stake in the success of the project. Working together in a proactive, open communication,
team oriented environment can aid in building a successful project and providing decision
makers with the necessary information to make the right decisions at the right time.

Each System Project must have a Program Sponsor

 To help ensure effective planning, management, and commitment to information systems,
each project must have a clearly identified program sponsor. The program sponsor serves in a
leadership role, providing guidance to the project team and securing, from senior management,
the required reviews and approvals at specific points in the life cycle. An approval from senior
management is required after the completion of the first seven of the SDLC phases, annually
during Operations and Maintenance Phase and six-months after the Disposition Phase. Senior
management approval authority may be varied based on dollar value, visibility level,
congressional interests or a combination of these. The program sponsor is responsible for
identifying who will be responsible for formally accepting the delivered system at the end of the
Implementation Phase.

A Single Project Manager must be Selected for Each System Project

The Project Manager has responsibility for the success of the project and works through a
project team and other supporting organization structures, such as working groups or user
groups, to accomplish the objectives of the project. Regardless of organizational affiliation, the
Project Manager is accountable and responsible for ensuring that project activities and decisions
consider the needs of all organizations that will be affected by the system. The Project Manager
develops a project charter to define and clearly identify thelines of authority between and within
the agency’s executive management, program sponsor, (user/customer), and developer for
purposes of management and oversight.

A Comprehensive Project Management Plan is Required for Each System Project

The project management plan is a pivotal element in the successful solution of an information
management requirement. The project management plan must describe how each life cycle phase
will be accomplished to suit the specific characteristics of the project. The project management
plan is a vehicle for documenting the project scope, tasks, schedule, allocated resources, and
interrelationships with other projects. The plan is used to provide direction to the many activities
of the life cycle and must be refined and expanded throughout the life cycle.

Specific Individuals Must be Assigned to Perform Key Roles throughout the Life Cycle
 Certain roles are considered vital to a successful system project and at least one
individual must be designated as responsible for each key role. Assignments may be made on a
full- or part-time basis as appropriate. Key roles include program/functional management,
quality assurance, security, telecommunications management, data administration, database
administration, logistics, financial, systems engineering, test and evaluation, contracts
management, and configuration management. For most projects, more than one individual
should represent the actual or potential users of the system.
 SYSTEM
REQUIREMENTS

 PROBLEM
FORMULATIO
N
 PROJECT
CATEGORY
 PLATFORM
 SYSTEM STUDY AND
PROBLEM FORMULATION

REQUIRMENTS ANALYSIS
SYSTEM STUDY AND PROBLEM FORMULATION

THE EXISTING SYSTEM

The existing system work manually. The existing system has got lot of intricacies within itself
and need lot of human effort and paper works. All above the data need to be maintained on
ledgers and maintaining this is a tedious and risky process. As the transactions increases, so the
data too. So the task of maintaining them increases exponentially. To view a data may need lot of
paper to be searched.

Some of the negative aspects of the existing system are as follows:

1) Course of action is time consuming. Wherever a need for search arises, the process evolves
search through paper records.

2) Readability of records is constrained. All the records may not be handled or written by the
same person. So the format and style of records differ and hence it is difficult to understand.

3) Paper records are easily damaged in course of time. The life time of paper record is unreliable
less that it easily gets spoiled.

4) Expenditure is high. Manual system needs added man power.

5) Prone to corruption by unauthorized users. Securing of manual system is not fully guaranteed.
Inaccuracy can be expected. Data can get easily scratched.

6) Techniques used are more complicated. Proper techniques are not exposed, so the functioning
is intricate.
 To overcome these, the proposed system has been suggested.

THE PROPOSED SYSTEM

The proposed system is a computerized one. This has greater accuracy and efficiency. This takes
only limited time for shopping.

The system includes two users.

1) Administrator(HR)

2) General User

The user gets into the system using user name and a unique password. Each user has his own
accessibility permission to accomplish his task flawlessly.

Advantages of the proposed system are-

1) Easy access to the data.

2) The new system is more user friendly, reliable and flexible.

3) Pop-up menus to carry out transactions for a new user, and for other alert messages.

4) Timely Report generation.

Requirement Analysis
At the heart of system analysis is a detailed understanding of all important facets of business area
under investigation. (For this reason, the process of acquiring this is often termed the detailed
investigation) Analyst, working closely with the employees and managers, must study the
business process to answer

these key questions are:

 What is being done?

 How is it being done?
 How frequent does it occur?
  How great is the volume of transaction or decisions
 How well is the task being performed?
 Does a problem exist?
 If a problem exist, how serious is it?
 If a problem exists, what is the underlying cause?

Requirement analysis relies on fact-finding techniques. These include:

 Interview
 Questionnaires
 Record
 inspection
 On-site observation

IDENTIFICATION OF NEED
In the world we are growing for globalization day by day with the development in IT resources
and advancement, by using latest technologies every organization wants to beat its competitors
and want to grow. Enterprise Resourceful Planning is the need of today’s organization. Survival
on manual system is difficult so, that’s why organization of the corporate world wants to
computerize their departments. The modules should be complete database driven and interactive
that should provide the proper information about the Placement and Training Organization.

Success of any system depends up to a large extent on how accurately a problem is

defined, thoroughly investigated and properly carried out to the choice of solution. Analysis is
the only phase in which the requirements for the new system are identified. System analysis is a
detailed study of the various operations performed by a system and their relationship within and
outside of the system. The question is: what must be done to solve the problem? One aspect of
analysis is defining the boundaries of the system and determining whether or not a candidate
system should consider other related system. During analysis data are collected on the available
files, decision points and transactions handled by the parent system. Data flow diagram,
interviews, onsite observations, questionnaires are used as a logical system model and tools to
perform the analysis.

An analyst is responsible for performing following tasks:

  Gathered all facts about the present system from the employees.
 Studied strength and weakness of the current system.
 Determined “what” must be done to solve the problem.
 Prepared a functional specifications document.

In order to reduce the time, there is a need for computerized system that cans retrieve data, insert
data, update existing data or delete existing data. These modules are developed wit the aim of
reducing time, reducing manpower, reducing cost so that the records can be easily maintained.
The volume of work and complexity are increasing year by year. This system reduces
complexity and workload.

PRELIMINARY INVESTIGATION
A request to take assistance from information system can be made for many reasons, but in each
case some one in the organization initiate the request. When the request is made, the first system
activity the preliminary investigation begins. This activity has three parts:

 Request clarification
 Feasible Study
 Request approval

Many requests from employees and users in the organization are not clearly defined. Therefore,
it becomes necessary that project request must be examined and clarified properly before
considering systems investigation.

The feasibility study is carried out by a small group of people who are familiar with information
system techniques, understand the parts of the business or organization that will be involved or
affected by the project, and are skilled in the system analysis and design process.

 Request Approval:
It is not necessary that all request projects are desirable or feasible. Some organizations receive
so many projects request from employees that only a few of them can be purchased. However,
those projects that are feasible and desirable should be put into a schedule.

In some cases, development can start immediately, although usually system staff members are
busy on other on-going projects. When such situation arises, management decides which projects
are more urgent and schedule them accordingly. After a project request is approved, its cost,
priority, completion time and personal requirements are estimated and used to determine where
to add it to any existing project list. Later on, when the other projects have been completed, the
proposed application development can be initiated.

Analysis is a process of studying a problem and to find the best solution to that problem.
System analysis gives us the target for the design and the implementation.

Analysis is one phase, which is important phase for system development life cycle.
System development is a problem solving techniques. Analysis involves interviewing the client
and the user. Three people and the existing documents about the current mode of operation are
the basic source of information for the analyst.

Analysis is the process of studying a problem to find the best solution to that problem. System
analysis gives us the target for the design and the implementation. Analysis is one phase of the
very important phase of the system development life cycle. System development is a problem
solving techniques. Analyses involve interviewing the client and the user. These people and the
existing document about the current mode of operation are the basic source of information for
the analyst.

Human Resource Department of the organization controls the manpower planning by recording
manpower requirements, grade, job specifications and presently vacancies and strength. It
maintains the candidate’s databank for the respective post.

SOFTWARE ENGINEERING PARADIGM

Computer Aided Software Engineering can be as simple as a single tool that support a specific
software engineering activity or as complex as a complete “environment “ that encompasses
tools, a database, people, hardware, a network, operating system, standards, and myriad other
components. Each building block forms a foundation for the next, with tools sitting as the top of
the heap. It is interesting to note that the foundation for effective CASE environment has
relatively little to do for software engineering tools themselves. Rather, successful environments
appropriate hardware and systems software. In addition, the environment architecture must
consider the human work patterns that are applied during the software engineering process.

The environment composed of the hardware platform and system support (including networking
software, software management, and object management services), the groundwork for CASE.
But the CASE environment itself demands other building blocks. A set of portability services
provides a bridge between CASE tools and their integration framework and the environment
architecture. The integration framework is a collection of specialized programs that enables
individual’s CASE tools to communicate one another, to create a project database, and to exhibit
the same look and feel to the end user (the software engineer). Portability services allow CASE
tools and their integration framework to migrate across different hardware platforms and
operating system without significant adaptive maintenance.

The building blocks represent a comprehensive foundation for the integration of CASE tools.
However, most CASE tools in use today have been: constructed using all these building blocks.

In fact some CASE tools remain “point solution:” That is, a tool is used to assist in a particular
software engineering activity (e.g. analysis modelling) but does not directly communicate with
other tools, is not tied into a project database, is not part of an integrated CASE environment (l-
CASE). Although this situation is not ideal, a CASE tool can be used quite effectively, even if it
is a point solution.

At the low end of the integration spectrum is the individual (point solution) tool. When
individual tools can provide tools provide facilities for data exchange, the integration level is
improved slightly. Such tools produce output in a standard format that should be compatible with
other tools that can read the format. In some cases, the builder of complementary CASE tools
work together to form a bridge between the tools (e.g. an analysis and design tool that is coupled
with a code generator). Using this approach, the team developed, synergy between the tools
separately. Single source integration occurs when a single CASE tools vendor integrates a
number of different tools and sells them as a package.
 Although this approach is quite effective, the closed architecture of most single source
environments precludes easy addition from other vendors.

3.0SOFTWARE REQUIREMENTSSPECIFICATIONS

SYSTEM REQUIREMENTS
Hardware Specification:-
It is recommended that the minimum configuration for clients is as appended below:-
Suggested Configuration of Windows clients:-
Microprocessor : - AMD E2-6110 APU with AMD Radeon R2
Graphics
Ram : - 4.00 GB (3.43 GB Usable)
Hard Disk : - 2.5 gigabytes (GB) on installation drive, which
includes 500 MB on system drive.
CD ROM Drive : - 52 X CD ROM Drive

Software Specifications:-

Operating System : Windows 10/Windows 7

RDBMS : MySql Server
Front End : JSP SERVLET
Web Designing : HTML, CSS JAVA SCRIPT

This system was developed under window XP/7,8. It is complete with all 32-bit versions of
windows operating system. Windows is a popular and largest used operating system in the world
because it is easy to understand and provides an easy interface to users.

Windows XP/7 Operating System

The main responsibility of an operating system is to manage computer’s resources. All activities in
the system scheduling application programs, waiting files to disk, sending data across a network
and so on should function as seamlessly and transparently as possible. Windows 98 makes your
computer easier to use, with new and enhanced feature.

Improved Reliability
Window xp,7, improves computer reliability by introducing new wizards, utilities and resources
that keep your system running smoothly.

Faster Operating System

Windows xp,7 includes tools that help your computer run faster than Windows xpwith out adding
new hardware. Window 7 includes a suite of programs designed to optimized you’re web.

Integration
Windows xp Explorer and Internet Explorer integrate local and Web-based resources in a single
viewer computer’s efficiency, especially when used together. Window xp,7 makes your computer
more entertaining by new hardware. These enhancements provide you with hours of fun.

Multitasking Concepts
Multitasking in general refers to an operating system’s capability to load and execute several
applications concurrently. A multitasking operating system is consider a robust and reliable one if
it successful shields concurrent applications from each other, making them believe that they
system also shields application from other’s bugs.
To a large extent, multitasking operating system relay on system hardware to implement these
capabilities. Another important aspect of multitasking is process scheduling. As process are
capable of executing only a single stream of instruction at any given, multitasking would
obviously not be possible without the technique of the context switching. A context switch,
triggered by a specific event (such as an interrupt from a timer circuit or a call by the running
application to a specific function), essentially consist of saving the processor context (instruction
pointer, stack pointer, register contents) of one running program and loading that of another.
In a cooperative multitasking environment, the operating system relies explicitly on
applications to yield control by regularly calling a specific set of operating system functions.
Context switching takes place at well-defined point during the execution of a program.
In a preemptive multitasking environment, the operating system can interrupt the
execution of an application at any time. This usually happens when the operating system responds
to hardware events, such as a interrupt from a timer circuit. An application’s flow of execution can
be interrupted at any point, not only at predefined spots. This realizes the complexity of the
system.
5.0 DESIGN
The most creative and challenging phase of the system life cycle is system design. The term
design describes a final system and the process by which it is developed. It refers to the technical
specifications that will be applied in implementing the candidate system.
The first step is to determine how the output is to be produced and in what format. Samples for
the output (and input) are also presented.
The second step is input data and master files (data base) have to be designed to meet the
requirements of the proposed output. The operational (processing) phases are handled through
program construction and testing including a list of the programs needed to meet the system’s
objective and complete documentation. Finally, details related to justification of the system on the
user and the organization are documented and evaluated by management as a step toward
implementation. To design the system we must note the following points:
 To identify the Software Components which satisfy the System Design.
 To design and document the Software Components and their linkage.

In this component the software components and relevant interfaces such as, interactions with
existing internal and external systems, network connections, standard input an output formats are
to be identified.

Identify Relevant Interfaces

 Interaction with existing internal systems.

 Interaction with external systems.
 Network Connections.
 Standard Input Formats
 Standard Output Formats.

Program Specification

Elements of Specifications required are:

 How it is being accessed.

 Function called.
 Program Security.
 Field Details. Program Functions.
STEPS IN SYSTEM DESIGN

Databases and database technology are having a major impact on the growing use of computers.
It is fair to say that databases will play critical role: in almost all areas where computers are used.
Including business, engineering, medicine, law, education and library, science to name a few. A
database is a collection of related data. By data we mean known facts that can be recorded and
that have implicit meaning for example, consider, the names, telephone numbers and addresses
of the people you know. You may have recorded this data in an indexed address, book, or you
may have stored it on a diskette. Using a personal computer and software such as DBASE IV or
V, PARADOX, MS EXCEL OR MS ACCESS. This is a collection of related data withanimplicit
meaning and hence is a database.
A database is a logically coherent of with some inherent meaning.
A database represents some aspects of the real world. Sometimes called the mini-world or the
universe of discourse (UOD). Changes to the mini-world are reflected in the database. A
database is designed, built and populated with data for the specific people. It has an intended
group of users and some preconceived applications in which the users are interested.
A database can be of any size and of varying complexity. For example, the list of names
and addresses referred to earlier may consist of only a few hundred records, each with simple
structure. On the other hand the card catalog of a large library may contain half a million cards
stored under different categories by primary author’s last name, by subject, by book title with
each category organized in alphabetic order.
A database may be generated and maintained or by machine. The library card catalog is
an example of a database that may be created and maintained either by a group of application
programs written specially for that task or by a database management system.
A database management system (DBMS) is a collection of programs that enables users to
create and maintained a database. The DBMS is hence a general-purpose software system that
facilities tile processed of defining, constructing and manipulating database for various
applications. Defining a database involves specifying the data types, structures and constraints
for the data to be stored in the database. Constructing the database is the process of storing the
data itself on some storage medium that is controlled by the DBMS. Manipulating a database
includes such functions as querying the database to reflect changes in the mini-world, and
generating reports form the data.
With the advent of the graphical operating system like windows, the world of imputing went
through a dramatic change. It opened up a whole new world of graphics. Interfaces that use
graphics came to known so graphical user interface (GUI). These became very popular because
the users could identify with images than words. Mention tile word print to a person and it
invokes the image of a printer. The primary requirements for an interface are that it is easy to
use. We must be able react intuitively to an interface presented to us. This is possible if the
interface presented is such that is it emulates real life.
FEASIBILITY STUDY

 TECHNIC
AL
 ECONOMI
CAL
 Feasibility Study

A feasibility study is conducted to select the best system that meets performance requirement.
This entails an identification description, an evaluation of candidate system and the selection of
best system for the job. The system required performance is defined by a statement of
constraints, the identification of specific system objective and a description of outputs.

The key consideration in feasibility analysis are :

1. Economic Feasibility :

2. Technical Feasibility :

3. Operational Feasibility:

Economical feasibility

It looks at the financial aspects of the project. It determines whether the management has enough
resources and budget to invest in the proposed system and the estimated time for the recovery of
cost incurred. It also determines whether it is worth while to invest the money in the proposed
project. Economic feasibility is determines by the means of cost benefit analysis. The proposed
system is economically feasible because the cost involved in purchasing the hardware and the
software are within approachable. The personal cost like salaries of employees hired are also
nominal, because working in this system need not required a highly qualified professional. The
operating-environment costs are marginal. The less time involved also helped in its economical
feasibility. It was observed that the organization has already using computers for other purpose,
so that there is no additional cost to be incurred for adding this system to its computers.

The backend required for storing other details is also the same database that is MySql. The
computers in the organization are highly sophisticated and don’t needsextra components to load
the software. Hence the organization can implement the new system without any additional
expenditure. Hence, it is economically feasible.

Technical Feasibility

It is a measure of the practically of a specific technical solution and the availability of technical
resources and expertise

 The proposed system uses Jsp/Servlet as front-end and Mysql as back-end tool.
 The above tools are readily available, easy to work with and widely used for developing
commercial application.

Hardware used in this project are- p4 processor 2.4GHz, 128 MB RAM, 40 GB hard disk, floppy
drive. This hardware was already available on the existing computer system. The software like
MySql Server and operating system WINDOWSXP’ used were already installed On the existing
computer system. So no additional hardware and software were required to purchase and it is
technically feasible. The technical feasibility is in employing computers to the organization. The
organization is equipped with enough computers so that it is easier for updating. Hence the
organization has not technical difficulty in adding this system.

Duration of Project:-
Operational Feasibility

The system will be used if it is developed well then be resistance for users that undetermined

 No major training and new skills are required as it is based on DBMS model.
 It will help in the time saving and fast processing and dispersal of user request and
applications.
 New product will provide all the benefits of present system with better performance.
 Improved information, better management and collection of the reports.
 User support.
 User involvement in the building of present system is sought to keep in mind the user
specific requirement and needs.
 User will have control over there own information. Important information such as payslip
can be generated at the click of a button.
 Faster and systematic processing of user application approval, allocation of IDs, payments,
etc. used had greater chances of error due to wrong information entered by mistake.

Behavioral Feasibility

People are inherent to change. In this type of feasibility check, we come to know if the newly
developed system will be taken and accepted by the working force i.e. the people who will use it.

SYSTEM DESIGN
 INTRODUCTIO
N
 DATA FLOW
DIAGRAM
 E-R
DIAGRAMS
 INTRODUCTION

SYSTEM DESIGN
5.1 Introduction

System design provides the understandings and procedural details necessary for implementing
the system recommended in the system study. Emphasis is on the translating the performance
requirements into design specifications. The design phase is a transition from a user-oriented
document (System proposal) to a document oriented to the programmers or database personnel.

System design goes through two phases of development:

1) Logical Design

2) Physical Design

A data flow diagram shows the logical flow of the system. For a system it
describes the input (source), output (destination), database (data stores) and procedures (data
flows) all in a format that meets the user’s requirement. When analysis prepare the logical
system design, they specify the user needs at a level of detail that virtually determines the
information flow into an out of the system and the required data resources. The logical design
also specifies input forms and screen layouts.

The activities following logical design are the procedure followed in the physical design e.g.,
producing programs, software, file and a working system. Design specifications instruct the user
about what the system should do.
Logical and Output Design:

The logical design of an information system is analogous to an engineering blue print of an

automobile. It shows the major features and how they are related to one another. The detailed
specification for the new system was drawn on the bases of user’s requirement data. The outputs
inputs and databases are designed in this phase.

Output design is one of the most important features of the information system. When the outputs
is not of good quality the users will be averse to use the newly designed system and may not use
the system. There are many types of output, all of which can be either highly useful or can be
critical to the users, depending on the manner and degree to which they are used.

Outputs from computer system are required primarily to communicate the results of processing
to users, They are also used to provide a permanent hard copy of these results for later
consultation. Various types of outputs required can be listed as below:

 External Outputs, whose destination is outside the organisation

 Internal outputs, whose destination is with the organisation
 Operational outputs, whose use is purely with in the computer department e.g., program-
listing etc.
 Interactive outputs, which involve the user is communicating directly with the computer, It
is particularly important to consider human factor when designing computer outputs. End
user must find outputs easy to use and useful to their jobs, Without quality output, user may
find the entire system unnecessary and avoid using it. The term “Output” in any
information system may apply to either printer or displayed information. During the
designing the output for this system, it was takeninto consideration, whether the
information to be presented in the form of query of report or to create documents etc.

Other important factors that were taken into consideration are:

The End user, who will use the output.

 The actual usage of the planned information

 The information that is necessary for presentation
 When and how often output and their format is needed. While designing output for project
based Attendance Compilation System, the following aspects of outputs designing were
taken into consideration.
  The outputs (i.e., well formatted table outputs in the screen itself) designed are simple to
read and interpret.
 Format of each output was another important point taken into consideration. Output media,
for each output appropriate media is decided whether it will be displayed on screen or will
be taken to printer or both.
 Other output design related specifications, i.e., how frequently the outputs will be
generated, how many pages or sheets approximately it will keep up, what is its planned use
and output distribution to users are also taken into account.

These were a few major designing issues, which were taken into consideration, while deciding
the output specifications for the system. As direct beneficiary of reports is the user community,
they were consulted constantly at every level. Formats and screen design for various reports were
identified, taking into account the user requirements. Before finalizing these were given to users
for any improvement and suggestions. End users issues taken into consideration were
Readability, Relevance and Acceptability.

Once all the output reports to be generated by ACS system were identified, they were given to
users for their acceptance. For prototyping various outputs, final outputs models were created
with dummy data, before they were finalized.

Output Sources:

Output contents originate from these sources:

 Retrieval from a data source.

 Transmission from a process or system activity.
 Directly from an input source.

The information produced in an output can be presented as:

 Tabular contents
 Graphic format
 Using Icons

Output Definition:

The output should be defined in terms of:

Types of outputs
  Content-headings, numeric, alphanumeric, etc.,
 Format-hardcopy, screen, microfilm, etc.,
 Location-local, remote, transmitted, etc.,
 Frequency-daily, weekly, hourly, etc.,
 Response-immediate with in a period, etc.,

Data items

 The name given to each data item should be recorded and its characteristics described
clearly in a standard form:
 Whether alphanumeric or numeric
 Legitimate and specific range of characteristics
 Number of characters
 Positions of decimal point, arithmetic design, etc.,

Input Design:
The input design is the link that ties the information system into the user’s world.
Input specifications describe the manner in which data enters the system for processing.
Input design features can ensure the reliability of the system and produce results from
accurate data, or they can result in the production of erroneous information.

Input Design consists of

 developing specifications and procedures for data preparation
 Steps necessary to put data into a usable form for processing.
 Data entry, the activity of putting data into the computer processing.

Objectives of Input design

Five objectives of design input focus on
 Controlling the amount of input required
 Avoid delay
 Avoiding errors in data
 Avoiding extra steps.
 Keeping the process simple.
 Input stages several activities have to be carried out as part of te overall input
process. They include some or all of the following.:
Data recording (i.e., collection of data)
Data encapsulation(i.e.,transfer of data)
Data conversion(i.,e.,controlling the flow of data)
Data transmission(i.e.,transportingte data)
Data validation(i.e.,checkingte input data)
Data correction(i.e.,correcting the errors)

Input Performa were designed, after a careful discussion with users. It was
attempted to cover all user requirements. Designed Performa were given to user for any
suggestion and final approval.
Various data items were identified and wherever necessary were recorded.
Input designs are aimed at reducing the chances of mistakes of errors. As the human beings
are prone to errors there is always a possibility of occurrence of chance of errors. Adequate
validation checks are incorporated to ensure error free data storage. Some of the data
validation checks applied are as following:
Redundancy of data is checked. It means the records of primary key do not occur twice.
Primary key field of any table must not be left blank.
Wherever items are coded, input code is checked for it’s validly with respect to several
checks.
Utmost care has been taken to incorporate the validation at each stage of the system.
Enough messages and dialogue boxes are provided while design screen, which does guide
user at the time of any errors, or at time of entry. This feature provides a user-friendly
interface to native users. It can be emphasized that input deigns of ONLINE CAREER
COUNSELING is so designed that it ensures easy and error free data entry mechanism.
Once one is sure of input data the output formatting becomes an routine work.

SOFTWARE DESIGN
The purpose of this phase is to plan a solution for the problem specified by the requirement
document. This is first step in moving from the problem domain to solution domain.
Designing activity is divided into two parts.
a) System DesignIt aims to identify the modules that should be in the system, the
specification of these modules and how they interact with each other to produce the desired
result.
b) Detailed Design The internal goal of each of the modules specified in the system is
decided.
 DATA FLOW DIAGRAM

5.2 Data Flow Diagram

Data Flow Diagramming is a means of representing a system at any level of detail with a
graphic network of symbols showing data flows, data stores, data processes, and data
sources/destination.
The data flow diagram is analogous to a road map. It is a network model of all possibilities with
different detail shown on different hierarchical levels. This processes of representing different
details level is called “leveling” or “partitioning” by some data flow diagram advocates. Like a
road map, there is no start point or stop point, no time or timing, or steps to get somewhere. We
just know that the data path must exist because at some point it will be needed. A road map
shows all existing or planned roads because the road is needed.
Details that is not shown on the different levels of the data flow diagram such as volumes,
timing, frequency, etc. is shown on supplementary diagrams or in the data dictionary. For
example, data store contents may be shown in the data dictionary.
Data Flow Diagram (DFD) uses a number of symbols to represent the systems.
Data Flow Diagram also known as ‘Bubble Chart’ is used to clarify system requirements
and identifying the major transformations that will become programs in system design. So it
isthe starting point of the design phase that functionally decomposes the requirements
specifications down to the level of details.

A square shows the Entity.

A Circle shows the Process.
An open Ended Rectangle shows the data store.
An arrow shows the data flow.
The DFD can be up to several levels. The 0 level DFD states the flow of data in the system
as seen from the outward in each module.
The first level DFD show more detail, about the single process of the 0 level DFD
The second level DFD can show even more details and so on.

Symbols of DFD:-
The Data flow Diagram shows the flow of data. It is generally made of symbols given
below:
The various symbols used for DFD are:

 Square

A square defines a source (originator) or destination of system data.

 Arrow

An arrow identifies data flow-data in motion. It is a pipeline through which information

flows.

 Circle

A circle or a bubble represents is a process that transforms incoming data flow into
outgoing data flow. Circle basically represents a process.

 Open Rectangle
 An open Rectangle is data store-data at rest, or temporary repository of data. Open
rectangle basically denotes data storage.

Information Flow of Data for Test:

 MODULAR DESIGN

Control Module Requirements

The control module forms the framework underlying the application, so it naturally has the most
high-level requirements. Extensibility and maintainability are prime considerations in this module.
The control module must be extensible because all realworld enterprise applications change
constantly. Because the control module plays a role in virtually every interaction, its code must be
well-structured to avoid complexity-related maintenance problems. The requirements of the control
module are:

 The module must handle all HTTP requests for the application. This module
controls a Web application, and interacts with a user who sends HTTP service
requests. The control module is responsible for classifying and dispatching each of
these requests to the other modules.
 HTTP responses may be of any content type. Web application developers do not
want to be limited to just textual content types. The control module must also be
able to produce binary responses.
 Business logic must be easily extensible. Enterprise applications are always
changing and growing as business rules and conditions change. A developer familiar
with the control module should be able easily to add new functionality with minimal
impact on existing functions.
 New views must be easy to add. Most business logic changes imply new user
views, so developers must be able to create new views easily.
 Module must provide application-wide control of look and feel. Manually editing
hundreds or dozens of user views is not a practical way to manage application
look and feel. The control module must provide a way for application screen
layout and style to be controlled globally.
 Application must be maintainable even as it grows. The control module must be
structured so that new functions added over time do not result in a thicket of
unmentionable “spaghetti” code. It should be possible to easily understand the
control of even an application with several hundred business classes.
  Application-wide functionality must be easy to add. New application requirements
occasionally apply to every operation or view in an application. The control

module must be structured so that such requirements can be easily met.

5.3 ENTITY RELATIONSHIP DIAGRAM

Data Flow Diagramming is a means of representing a system at any level of detail with a
graphic network of symbols showing data flows, data stores, data processes, and data
sources/destination.

Possibilities with different detail shown on different hierarchical levels. This processes of
representing different details level is called “leveling” or “partitioning” by some data flow
diagram advocates. Like a road map, there is no starting point or stop point, no time or timing, or
steps to get somewhere. We just know that the data path must exist because at some point it will
be needed. A road map shows all existing or planned roads because the road is needed.
Details that is not shown on the different levels of the data flow diagram such as volumes,
timing, frequency, etc. is shown on supplementary diagrams or in the data dictionary. For
example, data store contents may be shown in the data dictionary.

Data Flow Diagram (DFD) uses a number of symbols to represent the systems. Data
Flow Diagram also known as ‘Bubble Chart’ is used to clarify system requirements and
identifying the major transformations that will become programs in system design. So it is the
starting point of the design phase that functionally decomposes the requirements specifications
down to the level of details.
 Email
Password
Mobile

Registration
DOB
User

User
Password
Login

C Test

C++ Art.Lang.

Test
JAVA

Number series Analogies

5.4 DATABASE DESIGN
A database is a collection of inter-related data stored with a minimum of redundancy to serve
many applications. It minimizes the artificiality embedded in using separate files. The primary
objectives are fast response time to enquires, more information at low cost, control of
redundancy, clarity and ease of use, accuracy and fast recovery. The organization of data in a
database aims to achieve three major objectives, they are data integration, data integrity and data
independence. During the design of the database at most care has been taken to keep up the
objectives of the database design.

Database Tables:-

admin table
adminchat table

ctest table

chatting table

contact table
 feedback table

login table

registration table
CODE DESIGN
The process of code is to facilitate the identification and retrieve of items of information. The
code should be simple and easy to understandable. The codes were designed in such a way that
the features such as optimum human – oriented use and machine efficiency are unaffected.

For the code to be designed effectively, the following characteristics were also
considered while designing the code.

 Uniqueness
 Versatility
 Stability
 Simplicity
 Consciousness

The code should be adequate for present and anticipated data processing for machine and human
use. Care was taken to minimize the clerical effort and computer time required to continue
operation.

PROCESS DESIGN
The process can be conceptualized in such a way to keep the methodology of main module
process along with some auxiliary task, which will run concurrently with the main program.

The top-down approach is maintained so as to keep track of the process, which satisfies the
maintenance reliability testing requirements. The concurrency of the data is checked during data
entry, by means of validation check for data in each field.
5.5 Snapshots
5.6 Coding:-

Login
{% extends 'base.html' %}

{% load static %}

{% block 'content' %}

<h2 class="lh2">Login Form</h2>

{% for msg in messages %}

<div class="my-5 alert alert-danger" role="alert">

{{ msg }}

</div>

{% endfor %}

<form action="" method="POST">

{% csrf_token %}

<div>

<label for="username">Username:</label>

<input type="text" id="username" name="uname" required>

</div>

<div>

<label for="password">Password:</label>

<input type="password" id="password" name="pswd" required>

</div>

<div>

<button type="submit">Login</button>

<p class="mt-4">YOU DON'T HAVE AN ACCOUNT PLEASE&nbsp;&nbsp;<a

href="/signup">SIGN UP</a></p>
 </div>

</form>

{% endblock %}

Registration
{% extends 'base.html' %}

{% load static %}

{% block 'content' %}

<h2 class="sh2">Registration Form</h2>

{% for msg in messages %}

<div class="my-5 alert alert-danger" role="alert">

{{ msg }}

</div>

{% endfor %}

<form action="" method="POST">

{% csrf_token %}

<div>

<label for="first-name">First Name:</label>

<input type="text" id="first-name" name="fname" required>

</div>

<div>

<label for="last-name">Last Name:</label>

<input type="text" id="last-name" name="lname" required>

</div>

<div>

<label for="username">Username:</label>
 <input type="text" id="username" name="uname" required>

</div>

<div>

<label for="email">Email:</label>

<input type="email" id="email" name="email" required>

</div>

<div>

<label for="password">Password:</label>

<input type="password" id="password" name="pswd1" required>

</div>

<div>

<label for="confirm-password">Confirm Password:</label>

<input type="password" id="confirm-password" name="pswd2" required>

</div>

<div>

<button type="submit">Signup</button>

<p class="mt-4">YOU&nbsp; HAVE&nbsp; AN&nbsp; ACCOUNT&nbsp; PLEASE

&nbsp; &nbsp; <a href="/login">LOGIN</a></p>

</div>

</form>

{% endblock %}

Dashboard

{% extends 'base.html' %}
{% load static %}

{% block 'content' %}

<h1>Table Example</h1>

<div class="row mt-5 py-5">

<a href="/newblog" class="btn btn-primary">Add New</a>

</div>

<table>

<thead>

<tr>

<th>Image</th>

<th>Title</th>

<th>Description</th>

<th>Category</th>

<th>Written on</th>

<th>Last edited on</th>

<th>Actions</th>

</tr>

</thead>

<tbody>

{% for blog in blogs %}

<tr>

<td>

<img src="{{blog.imageURL}}" alt="" width="100px">

</td>

<<td><a href="blog/{{blog.id}}">{{ blog.title | truncatewords:5 }}</a></td>

 <td>{{ blog.discription | truncatewords:5 }}</td>

<td>{{ blog.category }}</td>

<td>{{ blog.created_at }}</td>

<td>{{ blog.edited_at }}</td>

<td>

<a href="delete/{{blog.id}}" class="btn btn-danger">Delete</a>

</td>

</tr>

{% endfor %}

</tbody>

</table>

{% endblock %}

Home Page

{% extends 'base.html' %}

{% load static %}

{% block 'content' %}

<!-- Page Content -->

<!-- Banner Starts Here -->

<div class="main-banner header-text">

<div class="container-fluid">

<div class="owl-banner owl-carousel">

{% for category in categories %}

 <div class="item">

<img src="{{category.imageURL}}" alt="">

<div class="item-content">

<div class="main-content">

<div class="meta-category">

<span>{{category.name}}</span>

</div>

</div>

</div>

</div>

{% endfor %}

</div>

</div>

</div>

<!-- Banner Ends Here -->

<section class="call-to-action">

<div class="container">

<div class="row">

<div class="col-lg-12">

<div class="main-content">

<div class="row">

<div class="col-lg-8">

<span>Read Blogs</span>

<h4>Creative Blog For Bloggers!</h4>

</div>

</div>
 </div>

</div>

</div>

</div>

</section>

<section class="blog-posts">

<div class="container">

<div class="row">

<div class="col-lg-8">

<div class="all-blog-posts">

<div class="row">

{% for blog in latest_three %}

<div class="col-lg-12">

<div class="blog-post">

<div class="blog-thumb">

<img src="{{blog.imageURL}}" alt="">

</div>

<div class="down-content">

<span>{{blog.category.name}}</span>

<a href="/blog/{{blog.id}}"><h4>{{blog.title}}</h4></a>

<ul class="post-info">

<li><a href="#">Published By : {{blog.author.name}}</a></li>

<li><a href="#">Published at : {{blog.created_at}}</a></li>

</ul>

<p>{{blog.discription|truncatewords:40}}</p>
 <div class="post-options">

<div class="row">

<div class="col-6">

<ul class="post-tags">

<li><i class="fa fa-tags"></i></li>

<li>{{blog.category.name}}</li>

</ul>

</div>

<div class="col-6">

<ul class="post-share">

<li><i class="fa fa-share-alt"></i></li>

<li>Last Edit : {{blog.edited_at}}</li>

</ul>

</div>

</div>

</div>

</div>

</div>

</div>

{% endfor %}

<div class="col-lg-12">

<div class="main-button">

<a href="blogs">View All Posts</a>

</div>

</div>

</div>

</div>
 </div>

<div class="col-lg-4">

<div class="sidebar">

<div class="row">

<div class="col-lg-12">

<div class="sidebar-item search">

<form id="search_form" name="gs" method="post" action="/search">

{% csrf_token %}

<input type="text" name="search" class="searchText" placeholder="type to

search..." autocomplete="on">

</form>

</div>

</div>

<div class="col-lg-12">

<div class="sidebar-item recent-posts">

<div class="sidebar-heading">

<h2>Recent Posts</h2>

</div>

<div class="content">

<ul>

{% for blog in latest_three %}

<li><a href="blog/{{blog.id}}">

<h5>{{blog.title}}</h5>

<span>{{blog.created_at}}</span>

</a></li>

{% endfor %}

</ul>
 </div>

</div>

</div>

<div class="col-lg-12">

<div class="sidebar-item categories">

<div class="sidebar-heading">

<h2>Categories</h2>

</div>

<div class="content">

<ul>

{% for category in categories %}

<li><a href="/category/{{category.name}}">- {{category.name}}</a></li>

{% endfor %}

</ul>

</div>

</div>

</div>

<!-- <div class="col-lg-12">

<div class="sidebar-item tags">

<div class="sidebar-heading">

<h2>Tag Clouds</h2>

</div>

<div class="content">

<ul>

<li><a href="#">Lifestyle</a></li>

<li><a href="#">Creative</a></li>

<li><a href="#">HTML5</a></li>
 <li><a href="#">Inspiration</a></li>

<li><a href="#">Motivation</a></li>

<li><a href="#">PSD</a></li>

<li><a href="#">Responsive</a></li>

</ul>

</div>

</div>

</div> -->

</div>

</div>

</div>

</div>

</div>

</section>

{% endblock %}
 TESTING

SYSTEM TESTING
Here the System testing involved is the most widely used testing process consisting of five stages
as shown in the figure. In general, the sequence of testing activities is component testing,
integration testing, and then user testing. However, as defects are discovered at any one stage,
Testing is the process of detecting errors. Testing performs a very critical role for quality
assurance and for ensuring the reliability of the software. The results of testing are used later on
during maintenance also.

Testing is vital to the success of the system. System testing makes a logical assumption that if
the parts of the system are correct, the goal will be successfully achieved. In adequate testing or
non-testing leads to errors that may not appear until months or even years later (Remember the
New York three day power failure due to a misplaced ‘Break’ statement).

This creates two problems:

1. The time lag between the cause and the appearance of the problem.

2. The time interval effect of the system errors on files and the records on the system.

A small error can conceivably explode into a much larger problem. Effective testing early in the
process translates directly into long term cost savings from a reduced number of errors.

Another reason for system testing is it’s utility as a user oriented vehicle before implementation.
The best program is worthless if it does not meet the user requirements. Unfortunately, the user’s
demands are often compromised by efforts to facilitate program or design efficiency in terms of
processing time or design efficiency.

Thus in this phase we went to test the code we wrote. We needed to know if the code compiled
with the design or not? Whether the code gave the desired outputs on given inputs? Whether it
was ready to be installed on the user’s computer or some more modifications were needed?

Through the web applications are characteristically different from there software counterparts
but the basic approach for testing these web applications is quite similar.

These basic steps of testing have been picked from software engineering practices. The
following are the steps, we undertook:

1. The content of the Intranet site is reviewed to uncover Content Errors. Content Errors covers
the typographical errors, grammatical errors, errors in content consistency, graphical
representation and cross referencing errors

2. The design model of the web application is reviewed to uncover the navigation errors. Use
cases, derived as a part of the analysis activity allows a web designer to exercise each usage
scenario against the architectural and navigational design. In essence these non-executable tests
help to uncover the errors in navigation.

3. When web applications are considered the concept of unit changes. Each web page
encapsulate content navigation links, content and processing elements(Forms, Scripts, JSP’s as
in our case). It is not always possible to test each of these individually. Thus is the base of the
web applications the unit to be considered is the web page. Unlike the testing of the algorithmic
details of a module the data that flows across the module interface, page level testing for web
applications is driven by content, processing and links encapsulating the web page.

4. The Assembled web application is tested for overall functionality and content delivery. the
various user cases are used that test the system for errors and mistakes.

5. The Web application is tested for a variety of environmental settings and is tested for various
configurations and upon various platforms.

Thread based testing is done to monitor the regression tests so that the site does not
become very slow is a lot of users are simultaneously logged on.

PSYCHOLOGY OF TESTING
` The aim of testing is often to demonstrate that a program works by showing that it has
no errors. The basic purpose of testing phase is to detect the errors that may be present in the
program. Hence one should not start testing with the intent ofshowing that a program works, but
the intent should be to show that a program doesn’t work. Testing is the process of executing a
program with the intent of finding errors.

TESTING OBJECTIVES:

The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say,

 Testing is a process of executing a program with the intent of finding an error.

 A successful test is one that uncovers an as yet undiscovered error.
  A good test case is one that has a high probability of finding error, if it exists. The tests
are inadequate to detect possibly present errors.
 The software more or less confirms to the quality and reliable standards.

LEVELS OF TESTING
In order to uncover the errors present in different phases, we have the concept of levels of
testing. The basic levels of testing are

Unit testing

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the
detailed design and the process specifications, testing is done to uncover errors within the
boundary of the module. All modules must be successful in the unit test before the start of the
integration testing begins.

In this project each service can be thought of a module. There are so many modules like Login,
HR Department, Interviewer Section, etc. Each module has been tested by giving different sets
of inputs. When developing the module as well as finishing the development, the module works
without any error. The inputs are validated when accepting them from the user.
Integration Testing

After unit testing, we have to perform integration testing. The goal here is to see if modules can
be integrated properly, the emphasis being on testing interfaces between modules. This testing
activity can be considered as testing the design and hence the emphasis on testing module
interactions.

In this project the main system is formed by integrating all the modules. When integrating all the
modules I have checked whether the integration effects working of any of the services by giving
different combinations of inputs with which the two services run perfectly before Integration.

System Testing

Here the entire software system is tested. The reference document for this process is the
requirements document, and the goal is to see if software meets its requirements. Here entire
‘CAREER COUNSELING’ has been tested against requirements of project and it is checked
whether all requirements of project have been satisfied or not.

ACCEPTANCE TESTING

Acceptance Testing is performed with realistic data of the client to demonstrate that the software
is working satisfactorily. Testing here is focused on external behavior of the system; the internal
logic of program is not emphasized.

Test cases should be selected so that the largest number of attributes of an equivalence class is
exercised at once. The testing phase is an important part of software development. It is the
process of finding errors and missing operations and also a complete verification to determine
whether the objectives are met and the user requirements are satisfied.

WHITE BOX TESTING

This is a unit testing method, where a unit will be taken at a time and tested thoroughly at a
statement level to find the maximum possible errors.

I tested step wise every piece of code, taking care that every statement in the code is executed at
least once. The white box testing is also called Glass Box Testing.
I have generated a list of test cases, sample data, which is used to check all possible
combinations of execution paths through the code at every module level.

White-box test focuses on the program control structure. Test cases are derived to ensure that all
statement in the program control structure. Test cases are derived to ensure that all statement in
the program control structure. Test cases are derived to ensure that all statement in the program
has been executed at least once during testing and that all logical conditions have been exercised.
Basis path testing, a white box technique, makes use of program graphs (or graph matrices) to
derive the set of linearly independent test that will ensure coverage. Condition and data flow
testing further exercising degrees of complexity.

BLACK BOX TESTING

This testing method considers a module as a single unit and checks the unit at interface and
communication with other modules rather getting into details at statement level. Here the module
will be treated as a block that will take some input and generate output. Output for a given set of
input combinations are forwarded to other modules.

Black-box test are designed to uncover errors functional requirement without regard to the
internal workings of a program. Black-box testing techniques focus on the information domain
of the software, deriving test cases by partitioning the input and output domain of a program in
manner that provides through test coverage. The black-box test is used to demonstrate that
software functions are operational, that input is properly produced, and that the integrity of
external information are maintained. A black-box test examines some fundamental aspect of a
system with little or no regard for the integral logical structure of the software.

Graph based testing methods explore the relationship between and behavior of program objects.
Equivalence partitioning divides the input classes of data are likely to exercise specific software
function. Boundary values analysis probes the program’s ability to handle data at the limits of
acceptability.

TEST INFORMATION FLOW

A strategy for software testing may also be viewed in the context of the spiral. Unit testing
begins at the vortex of the spiral and, concentrates on each unit, component of the software as
implemented in source code. Testing progresses moving outward along the spiral to integration
testing, where the focus is on designed the construction of the software architecture. Taking
another turn outward on spiral, we encounter validation testing, where requirements established
as part of software requirements analysis are validated against the software that has been
constructed. Finally, we arrive at system testing, where the software and other system elements
are tested as a whole. To test computer software, we spiral out along stream lines that broaden
the scope of testing with each turn.

Considering the process from a procedural point of view, testing within the context of software
engineering is actually a series of four steps that are implemented sequentially. The steps are
shown in Figure. Initially, tests focus on each component individually, ensuring that it functions
properly as unit. Hence, the name unit testing. Unit testing makes heavy use of white-box testing
techniques, exercising specific paths in module’s control structure to ensure complete coverage
and maximum error detection.
 QUALITY
ASSURANCE

QUALITY ASSURANCE

INTRODUCTION

The key factor to the success in software quality program is its implementation. While definition
of process can be evolving phenomenon, implementation of processes makes the difference
between success & failure.

A quality product can be defined as:

 One that is fit for use.

 One that is produced as per the predefined standards.

So, Software Quality Assurance is the process of ensuring that the product confirms to its
standards.

QUALITY MANAGEMENT SYSTEM

A Quality Management System (QMS) is instituted by an organization to manage & maintain

quality procedures in its day-to-day functioning. It is a conglomerate of people who have the
required authority, responsibility and procedures for performing various activities. The QMS of
an organization is guided by quality policy & quality procedures supported by various
documents-Forms/Formats to maintain records & work instructions to provide guidelines for
doing a particular piece of work.
IMPLEMENTATION
&
MAINTENANCE

 IMPLEMEN
TATION
 EVALUATI
ON
 IMPLEMENTATION

IMPLEMENTATION

Introduction

System implementation is the stage when the user has thoroughly tested the system and approves
all the features provided by the system. The various tests are performed and the system is
approved only after all the requirements are met and the user is satisfied.

The new system may be totally new, replacing an existing manual or automated system,
or it may be a major modification to an existing system. In either case, proper implementation is
essential to provide a reliable system to meet organizational requirements. Successful
implementation may not guarantee improvement in the organization using the new system (that
is a design question), but improper will prevent it.

Implementation is the process of having systems personnel check out and put new
equipment into use, train users, install the new application and construct any files of data needed
to use it. This phase is less creative than system design. Depending on the size of the
organization that will be involved in using the application and the risk involved in its use,
systems developers may choose to test the operation in only one area of the firm with only one or
two persons. Sometimes, they will run both old and new system in parallel way to com-pare the
results. In still other situations, system developers stop using the old system one day and start
using the new one the next.

The implementation of the web based or LAN based networked project has some extra
steps at the time of implementation. We need to configure the system according the requirement
of the software.

For the project we need to install and configure Weblogic server 8.1 , database server, and the
deployment directory for the project.
Aspects of Implementation

The two aspects of implementation are:

 Training Personnel
 Conversion Procedures

TRAINING

Even well designed and technically elegant systems can succeed or fail because of the way they
are used. Therefore the quality of the training received by the personnel involved with the system
in various ways helps or hinders, and may even prevent, the successful implementation of an
information system.

Since, ONLINE CAREER COUNSELING System is web-based and user friendly, not
much effort was required in training process.

CONVERSION:

Conversion is the process of changing from the old system to the new system. There are
two methods of handling systems conversion:

 Parallel Run
 Immediate cut-off

Parallel Run

In this approach, the old system and the new system are used simultaneously for some
period of time so that the performance of the new system can be monitored and compared with
that of the old system. Also in case of failure of the new system, the user can fall back on the old
system. The risk of this approach is that the user may never want to shift to new system.

9.2.2.1 Immediate cut-off

In this method, the use of the old system ceases as soon as the new system is implemented and
bought in to palace. The old system becomes redundant from the day of implementation of the
new system. There is the high risk involved in this approach if the new system is not tested
rigorously. This is because of the fact that if the new system fails, then there will not be anything
to fall back upon. The advantage of this approach is that both the systems need not be used
simultaneously.

Implementation Tools

The project was implemented using Java server pages, HTML, Java beans. The
implementation work was carried out in Windows XP/7,8 platform.

1) JSP/SERVLET

2) GLASS-FISH

3) MySql Server

Coding

 This means program construction with procedural specifications has finished and the
coding for the program begins:
 Once the design phase was over, coding commenced.
 Coding is natural consequence of design. Coding step translate a detailed design
representation of software into a programming language realization.
 Main emphasis while coding was on style so that the end result was an optimized code.

The following points were kept into consideration while coding: Coding Style The structured
programming method was used in all the modules the project. It incorporated the following
features:

 The code has been written so that the definition and implementation of each function is
contained in one file.
 A group of related function was clubbed together in one file to include it when needed
and save us from the labor of writing it again and again.

Naming Convention:-

 As the project size grows, so does the complexity of recognizing the purpose of the
variables. Thus the variables were given meaningful names, which would help in
understanding the context and the purpose of the variable.
 The function names are also given meaningful names that can be easily understood by the
user.
Indentation

Judicious use of indentation can make the task of reading and understanding a program much
simpler. Indentation is an essential part of a google program. If code id intended without thought
it will seriously affect the readability of the program.

 The higher-level statements like he definition of the variables, constants and the function
are intended, with each nested block intended, stating their purpose in the code.
 Blank line is also left between each function definition to make the code look neat.
 Indentation for each source file stating the purpose of the file is also done.

MAINTENANCE
 MAINTENANCE
Maintenance or enhancement can be classified as: -

 Corrective
 Adaptive
 Perfective.

Corrective maintenance means repairing processing or performance failures or making changes

because of previously uncorrected problems or false assumptions.

Adaptive maintenance means changing the program function.

Perfective maintenance means enhancing the performance or modifying the program(s)

to respond to the user’s additional or changing needs.

Maintenance is actually the implementation of the post implementation review plan.

As important as it is, many programmers and analysts are reluctant to perform or identify
themselves with the maintenance effort. There are psychological, personality and professional
reasons for this. In any case, a first class effort must be made to ensure that software changes are
made properly and in time to keep the system in tune with user specifications.

Maintenance is costly. One way to reduce maintenance costs is through maintenance

management and software modification audits. Software modification consists of program
rewrites system level updates, and re-audits of low ranking programs to verify and correct the
soft spots.

The outcome should be more reliable software, a reduced maintenance backlog, and
higher satisfaction and morale among the maintenance staff.
 In Online Career Counseling, care has been taken towards maintenance; Loop Holes can
be eradicated from the system from time to time according to changing requirements with lesser

cost.

EVALUATION
 EVALUATION
The evaluation phase ranks vendor proposals and determines the one best suited, Evaluation of
the system is performed to identify its strengths and weaknesses. The actual evaluation can occur
along any of the following dimensions:

 Operational Evaluation: Assessment of the manner in which the system functions,

including case of use, response time, overall reliability and level of utilization.
 Organizational Impact: Identification and measurement of benefits to the organization in
such areas as financial concerns, operational efficiency and competitive impact.
 User Manager Assessment Evaluation of the attitudes of senior and user manager within
the organization, as well as end-users.

Development Performance: Evaluation of the development process in accordance with

such yardsticks as overall development time and effort, conformance to budgets and standards
and other project management criteria.

System Development Methodology

System Development Life Cycle

PHASES:

1.2.1 Initiation Phase

The initiation of a system (or project) begins when a business need or opportunity is identified. A
Project Manager should be appointed to manage the project. This business need is
EVALUATION documented in a Concept Proposal. After the Concept Proposal is approved, the
System Concept Development Phase begins.

1.2.2 System Concept Development Phase

Once a business need is approved, the approaches for accomplishing the concept are
reviewed for feasibility and appropriateness. The Systems Boundary Document identifies the
scope of the system and requires Senior Official approval and funding before beginning the
Planning Phase.

1.2.3 Planning Phase

 The concept is further developed to describe how the business will operate once the
approved system is implemented, and to assess how the system will impact employee and
customer privacy. To ensure the products and /or services provide the required capability on-
time and within budget, project resources, activities, schedules, tools, and reviews are defined.
Additionally, security certification and accreditation activities begin with the identification of
system security requirements and the completion of a high level vulnerability assessment.

1.2.4 Requirements Analysis Phase

Functional user requirements are formally defined and delineate the requirements in
terms of data, system performance, security, and maintainability requirements for the system. All
requirements are defined to a level of detail sufficient for systems design to proceed. All
requirements need to be measurable and testable and relate to the business need or opportunity
identified in the Initiation Phase.

1.2.5 Design Phase

The physical characteristics of the system are designed during this phase. The operating
environment is established, major subsystems and their inputs and outputs are defined, and
processes are allocated to resources. Everything requiring user input or approval must be
documented and reviewed by the user. The physical characteristics of the system are specified
and a detailed design is prepared. Subsystems identified during design are used to create a
detailed structure of the system. Each subsystem is partitioned into one or more design units or
modules. Detailed logic specifications are prepared for each software module.

1.2.6 Development Phase

The detailed specifications produced during the design phase are translated into
hardware, communications, and executable software. Software shall be unit tested, integrated,
and retested in a systematic manner. Hardware is assembled and tested.

1.2.7 Integration and Test Phase

 The various components of the system are integrated and systematically tested. The user
tests the system to ensure that the functional requirements, as defined in the functional
requirements document, are satisfied by the developed or modified system. Prior to installing and
operating the system in a production environment, the system must undergo certification and
accreditation activities.

1.2.8 Implementation Phase

The system or system modifications are installed and made operational in a production
environment. The phase is initiated after the system has been tested and accepted by the user.
This phase continues until the system is operating in production in accordance with the defined
user requirements.

1.2.9 Operations and Maintenance Phase

The system operation is ongoing. The system is monitored for continued performance in
accordance with user requirements, and needed system modifications are incorporated. The
operational system is periodically assessed through In-Process Reviews to determine how the
system can be made more efficient and effective. Operations continue as long as the system can
be effectively adapted to respond to an organization’s needs. When modifications or changes are
identified as necessary, the system may reenter the planning phase.

1.2.10 Disposition Phase

The disposition activities ensure the orderly termination of the system and preserve the
vital information about the system so that some or all of the information may be reactivated in
the future if necessary. Particular emphasis is given to proper preservation of the data processed
by the system, so that the data is effectively migrated to another system or archived in
accordance with applicable records management regulations and policies, for potential future
access.

SDLC Objectives

This guide was developed to disseminate proven practices to system developers, project
managers, program/account analysts and system owners/users throughout the DOJ. The specific
objectives expected include the following:

 To reduce the risk of project failure

  To consider system and data requirements throughout the entire life of the system
 To identify technical and management issues early
 To disclose all life cycle costs to guide business decisions
 To foster realistic expectations of what the systems will and will not provide
 To provide information to better balance programmatic, technical, management, and cost
aspects of proposed system development or modification.
 To encourage periodic evaluations to identify systems that are no longer effective
 To measure progress and status for effective corrective action
 To support effective resource management and budget planning
 To consider meeting current and future business requirements

Key Principles

This guidance document refines traditional information system life cycle management
approaches to reflect the principles outlined in the following subsections. These are the
foundations for life cycle management.

Life Cycle Management Should be used to Ensure a Structured Approach to Information

Systems Development, Maintenance, and Operation.

This SDLC describes an overall structured approach to information management.

Primary emphasis is placed on the information and systems decisions to be made and the proper
timing of decisions. The manual provides a flexible framework for approaching a variety of
systems projects. The framework enables system developers, project managers, program/account
analysts, and system owners/users to combine activities, processes, and products, as appropriate,
and to select the tools and methodologies best suited to the unique needs of each project.

Support the use of an Integrated Product Team

The establishment of an Integrated Product Team (IPT) can aid in the success of a project. An
IPT is a multidisciplinary group of people who support the Project Manager in the planning,
execution, delivery and implementation of life cycle decisions for the project. The IPT is
composed of qualified empowered individuals from all appropriate functional disciplines that
have a stake in the success of the project. Working together in a proactive, open communication,
team oriented environment can aid in building a successful project and providing decision
makers with the necessary information to make the right decisions at the right time.
Each System Project must have a Program Sponsor

To help ensure effective planning, management, and commitment to information systems,

each project must have a clearly identified program sponsor. The program sponsor serves in a
leadership role, providing guidance to the project team and securing, from senior management,
the required reviews and approvals at specific points in the life cycle. An approval from senior
management is required after the completion of the first seven of the SDLC phases, annually
during Operations and Maintenance Phase and six-months after the Disposition Phase. Senior
management approval authority may be varied based on dollar value, visibility level,
congressional interests or a combination of these.

The program sponsor is responsible for identifying who will be responsible for formally
accepting the delivered system at the end of the Implementation Phase.

A Single Project Manager must be Selected for Each System Project

The Project Manager has responsibility for the success of the project and works through a project
team and other supporting organization structures, such as working groups or user groups, to
accomplish the objectives of the project. Regardless of organizational affiliation, the Project
Manager is accountable and responsible for ensuring that project activities and decisions
consider the needs of all organizations that will be affected by the system. The Project Manager
develops a project charter to define and clearly identify the lines of authority between and within
the agency’s executive management, program sponsor, (user/customer), and developer for
purposes of management and oversight.

A Comprehensive Project Management Plan is Required for Each System Project

The project management plan is a pivotal element in the successful solution of an information
management requirement. The project management plan must describe how each life cycle phase
will be accomplished to suit the specific characteristics of the project. The project management
plan is a vehicle for documenting the project scope, tasks, schedule, allocated resources, and
interrelationships with other projects. The plan is used to provide direction to the many activities
of the life cycle and must be refined and expanded throughout the life cycle.
Specific Individuals Must be Assigned to Perform Key Roles Throughout the Life Cycle
Certain roles are considered vital to a successful system project and at least one
individual must be designated as responsible for each key role. Assignments may be made on a
full- or parttime basis as appropriate. Key roles include program/functional management, quality
assurance, security, telecommunications management, data administration, database
administration, logistics, financial, systems engineering, test and evaluation, contracts
management, and configuration management. For most projects, more than one individual
should represent the actual or potential users of the system (that is, program staff) and should be
designated by the Program Manager of the program and organization.
Process Engineering of Application Software (Software Development Life cycle)

Identification of the need

Since the world is growing for globalization, every organization wants to beat its competitors
and want to grow. Enterprise Resourceful Planning (ERP) is the need of today’s organization.
Survival on manual system is difficult so, that’s why organization of the corporate world wants
to computerize their departments. The modules should be complete database driven and
interactive that should provide the proper information about the Placement and Training
Organization.
Success of a system depends largely on how accurately a problem is defined, thoroughly
investigated and properly carried out to the choice of solution. Analysis is a phase in which the
requirements for the new system are identified. System analysis is a detailed study of the various
operations performed by a system and their relationship within and outside of the system. The
question is: what must be done to solve the problem? One aspect of analysis is defining the
boundaries of the system and determining whether or not a candidate system should consider
other related system. During analysis data are collected on the available files, decision points and
transactions handled by the parent system. Data flow diagram, interviews, onsite observations,
questionnaires are used as a logical system model and tools to perform the analysis.

Tasks, which are performed as analyst:

 Gathered all facts about the present system from the employees.
 Studied strength and weakness of the current system.
 Determined “what” must be done to solve the problem.
 Prepared a functional specifications document.

In order to reduce the time, there is a need for computerized system that cans retrieve data, insert
data, update existing data or delete existing data. These modules are developed wit the aim of
reducing time, reducing manpower, reducing cost so that the records can be easily maintained.
The volume of work and complexity are increasing year by year. This system reduces
complexity and workload.

1.1 Preliminary Investigation:

A request to take assistance from information system can be made for many reasons, but in each
case someone in the organization initiate the request. When the request is made, the first system
activity the preliminary investigation begins.
This activity has three parts:
 Request clarification
 Feasible Study
 Request approval
Many requests from employees and users in the organization are not clearly defined. Therefore,
it becomes necessary that project request must be examined and clarified properly before
considering systems investigation.
The feasibility study is carried out by a small group of people who are familiar with information
system techniques, understand the parts of the business or organization that will be involved or
affected by the project, and are skilled in the system analysis and design process.
Request Approval:
It is not necessary that all request projects are desirable or feasible. Some organizations receive
so many projects request from employees that only a few of them can be purchased. However,
those projects that are feasible and desirable should be put into a schedule. In some cases,
development can start immediately, although usually system staff members are busy on other
ongoing projects. When such situation arises, management decides which projects are more
urgent and schedule them accordingly. After a project request is approved, its cost, priority,
completion time and personal requirements are estimated and used to determine where to add it
to any existing project list. Later on, when the other projects have been completed, the proposed
application development can be initiated.
Analysis is a process of studying a problem and to find the best solution to that problem. System
analysis gives us the target for the design and the implementation. Analysis is one phase, which
is important phase for system development lie cycle. System development is a problem solving
techniques. Analysis involves interviewing the client and the user. Thee people and the existing
documents about the current mode of operation are the basic source of information for the
analyst.
Analysis is the process of studying a problem to find the best solution to that problem. System
analysis gives us the target for the design and the implementation. Analysis is one phase of the
very important phase of the system development life cycle. System development is a problem
solving techniques. Analyses involve interviewing the client and the user. These people and the
existing document about the current mode of operation are the basic source of information for
the analyst.

2.0 SOFTWARE ENGINEERING PARADIGM APPLIED

Computer Aided Software Engineering can be as simple as a single tool that support a specific
software engineering activity or as complex as a complete “environment “ that encompasses
tools, a database, people, hardware, a network, operating system, standards, and myriad other
components. Each building block forms a foundation for the next, with tools sitting as the top of
the heap. It is interesting to note that the foundation for effective CASE environment has
relatively little to do for software engineering tools themselves. Rather, successful environments
appropriate hardware and systems software. In addition, the environment architecture must
consider the human work patterns that are applied during the software engineering process.
The environment composed of the hardware platform and system support (including networking
software, software management, and object management services), the groundwork for CASE.
But the CASE environment itself demands other building blocks. A set of portability
services provides a bridge between CASE tools and their integration framework and the
environment architecture. The integration framework is a collection of specialized programs that
enables individual’s CASE tools to communicate one another, to create a project database, and to
exhibit the same look and feel to the end user (the software engineer). Portability services allow
CASE tools and their integration framework to migrate across different hardware platforms and
operating system with out significant adaptive maintenance.
The building blocks represent a comprehensive foundation for the integration of CASE
tools. However, most CASE tools in use today have been: constructed using all these building
blocks. In fact some CASE tools remain “point solution:” That is, a tool is used to assist in a
particular software engineering activity (e.g. analysis modeling) but does not directly
communicate with other tools, is not tied into a project database, is not part of an integrated
CASE environment (l-CASE). Although this situation is not ideal, a CASE tool can be used quite
effectively, even if it is a point solution.
At the low end of the integration spectrum is the individual (point solution) tool. When
individual tools can provide tools provide facilities for data exchange, the integration level is
improved slightly. Such tools produce output in a standard format that should be compatible with
other tools that can read the format. In some cases, the builder of complementary CASE tools
work together to form a bridge between the tools (e.g. an analysis and design tool that is coupled
with a code generator). Using this approach, the team develops, synergy between the tools
separately. Single source integration occurs when a single CASE tools vendor integrates a
number of different tools and sells them as a package.
Although this approach is quite effective, the closed architecture of most single source
environments precludes easy addition from other vendors.
BIBLIOGRAPHY
11.0 Bibliography

BOOKS

The Complete Reference 7th edition(Herbert Schildt)

Html css the complete reference 5th edition(Thomas A.Powell)

CSS Programming CookBook(Fabio Cimo)

WEBSITES

 http://www.java4us.com
 http://www.javacode.com
 http://www.journaldev.com
 http://www.roseindia.com
 http://www.youtube.com
 http://www.w3school.com