Computer Institute Management System
Computer Institute Management System
A
01 ACKNOWLEDGEMENT
02 INTRODUCTION 02
03
04 PROPOSED SYSTEM
09
07 FLOW CHART
08 SOURCE CODES 10
09 OUTPUTS 17
21
10 TESTING
11 INSTALLING PROCESS 24
12 25
HARDWARE AND SOFTWARE REQUIREMENTS
13 BIBLIPGRAPHY 26
1
PROJECT ON COMPUTER INSTITUTE MANAGEMENT SYSTEM
INTRODUCTION
The Computer Institute Management System is a software used to register oneself for a
Note :
• Allow the administrator to delete an enrollment, edit the name and course of a candidate.
The objective of this project is to let the students apply the programming knowledge into a
real- world situation/problem and exposed the students how programming skills helps in developing
a good software.
• Apply object oriented programming principles effectively when developing small to medium
sized projects.
• Students will demonstrate ability to conduct a research or applied Computer Science project,
requiring writing and presentation skills which exemplify scholarly style in computer science.
2
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really wants to stand
against today’s merciless competition where not to wise saying “to err is human” no longer valid,
it’s outdated to rationalize your mistake. So, to keep pace with time, to bring about the best result
without malfunctioning and greater efficiency so to replace the unending heaps of flies with a much
One has to use the data management software. Software has been an ascent in atomization
various organizations. Many software products working are now in markets, which have helped in
making the organizations work easier and efficiently. Data management initially had to maintain a
lot of ledgers and a lot of paper work has to be done but now software product on this organization
has made their work faster and easier. Now only this software has to be loaded on the computer
This prevents a lot of time and money. The work becomes fully automated and any
information regarding the organization can be obtained by clicking the button. Moreover, now it’s
an age of computers of and automating such an organization gives the better look.
3
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
The systems development life cycle is a project management technique that divides
complex projects into smaller, more easily managed segments or phases. Segmenting projects
allows managers to verify the successful completion of project phases before allocating resources
to subsequent phases.
Software development projects typically include initiation, planning, design, development,
testing, implementation, and maintenance phases. However, the phases may be divided differently
depending on the organization involved.
For example, initial project activities might be designated as request, requirements-
definition, and planning phases, or initiation, concept-development, and planning phases. End
users of the system under development should be involved in reviewing the output of each phase
to ensure the system is being built to deliver the needed functionality.
INITIATION PHASE
The Initiation Phase begins when a business sponsor identifies a need or an opportunity.
4
• Identify and validate an opportunity to improve business accomplishments of the
organization or a deficiency related to a business need.
• Identify significant assumptions and constraints on solutions to that need.
• Recommend the exploration of alternative concepts and methods to satisfy the need
including questioning the need for technology, i.e., will a change in the business process
offer a solution?
• Assure executive business and executive technical sponsorship. The Sponsor designates
a Project Manager and the business need is documented in a Concept Proposal. The
Concept Proposal includes information about the business process and the relationship to
the Agency/Organization.
• Infrastructure and the Strategic Plan. A successful Concept Proposal results in a Project
Management Charter which outlines the authority of the project manager to begin
the project.
Careful oversight is required to ensure projects support strategic business objectives and
resources are effectively implemented into an organization's enterprise architecture. The initiation
phase begins when an opportunity to add, improve, or correct a system is identified and formally
requested through the presentation of a business case. The business case should, at a minimum,
describe a proposal’s purpose, identify expected benefits, and explain how the proposed system
supports one of the organization’s business strategies. The business case should also identify
alternative solutions and detail as many informational, functional, and network requirements as
possible.
The System Concept Development Phase begins after a business need or opportunity is validated
by the Agency/Organization Program Leadership and the Agency/Organization CIO.
5
• Establish system boundaries; identify goals, objectives, critical success factors, and
performance measures.
• Evaluate costs and benefits of alternative approaches to satisfy the basic functional
requirements
• Assess project risks
• Identify and initiate risk mitigation actions, and Develop high-level technical architecture,
process models, data models, and a concept of operations. This phase explores potential
technical solutions within the context of the business need.
• It may include several trade-off decisions such as the decision to use COTS software
products as opposed to developing custom software or reusing software components, or the
decision to use an incremental delivery versus a complete, onetime deployment.
• Construction of executable prototypes is encouraged to evaluate technology to support the
business process. The System Boundary Document serves as an important reference
document to support the Information Technology Project Request (ITPR) process.
• The ITPR must be approved by the State CIO before the project can move forward.
PLANNING PHASE
6
The planning phase is the most critical step in completing development, acquisition, and
maintenance projects. Careful planning, particularly in the early stages of a project, is necessary
to coordinate activities and manage project risks effectively. The depth and formality of project
plans should be commensurate with the characteristics and risks of a given project. Project plans
refine the information gathered during the initiation phase by further identifying the specific activities
and resources required to complete a project.
A critical part of a project manager’s job is to coordinate discussions between user, audit,
security, design, development, and network personnel to identify and document as many
functional, security, and network requirements as possible. During this phase, a plan is developed
that documents the approach to be used and includes a discussion of methods, tools, tasks,
resources, project schedules, and user input. Personnel assignments, costs, project schedule, and
target dates are established.
A Project Management Plan is created with components related to acquisition planning,
configuration management planning, quality assurance planning, concept of operations, system
security, verification and validation, and systems engineering management planning.
This phase formally defines the detailed functional user requirements using high-level
requirements identified in the Initiation, System Concept, and Planning phases. It also delineates
the requirements in terms of data, system performance, security, and maintainability requirements
for the system. The requirements are defined in this phase to a level of detail sufficient for systems
design to proceed. They need to be measurable, testable, and relate to the business need or
opportunity identified in the Initiation Phase. The requirements that will be used to determine
acceptance of the system are captured in the Test and Evaluation Master Plan.
• Further define and refine the functional and data requirements and document them in the
Requirements Document,
• Complete business process reengineering of the functions to be supported (i.e., verify
what information drives the business process, what information is generated, who
generates it, where does the information go, and who processes it),
7
• Develop detailed data and process models (system inputs, outputs, and the process.
• Develop the test and evaluation requirements that will be used to determine acceptable
system performance.
DESIGN PHASE
The design phase involves converting the informational, functional, and network
requirements identified during the initiation and planning phases into unified design specifications
that developers use to script programs during the development phase. Program designs are c
constructed in various ways. Using a top-down approach, designers first identify and link major
program components and interfaces, then expand design layouts as they identify and link smaller
subsystems and connections. Using a bottom-up approach, designers first identify and link minor
program components and interfaces, then expand design layouts as they identify and link larger
systems and connections. Contemporary design techniques often use prototyping tools that build
mock-up designs of items such as application screens, database layouts, and system
architectures. End users, designers, developers, database managers, and network administrators
should review and refine the prototyped designs in an iterative process until they agree on an
acceptable design. Audit, security, and quality assurance personnel should be involved in the
review and approval process. During this phase, the system is designed to satisfy the functional
requirements identified in the previous phase. Since problems in the design phase could be very
expensive to solve in the later stage of the software development, a variety of elements are
considered in the design to mitigate risk. These include:
8
• Everything requiring user input or approval is documented and reviewed by the user. Once
these documents have been approved by the Agency CIO and Business Sponsor, the final
System Design Document is created to serve as the Critical/Detailed Design for the system.
• This document receives a rigorous review by Agency technical and functional
representatives to ensure that it satisfies the business requirements. Concurrent with the
development of the system design, the Agency Project Manager begins development of the
Implementation Plan, Operations and Maintenance Manual, and the Training Plan.
DEVELOPMENT PHASE
• Subsystem integration, system, security, and user acceptance testing is conducted during
the integration and test phase. The user, with those responsible for quality assurance,
validates that the functional requirements, as defined in the functional requirements
document, are satisfied by the developed or modified system. OIT Security staff assess the
system security and issue a security certification and accreditation prior to
installation/implementation.
9
Multiple levels of testing are performed, including:
• Testing at the development facility by the contractor and possibly supported by end users
• Testing as a deployed system with end users working together with contract personnel
• Operational testing by the end user alone performing all functions. Requirements are
traced throughout testing, a final Independent Verification & Validation evaluation is
performed and all documentation is reviewed and accepted prior to acceptance of the
system.
IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted by the user. In this
phase, the system is installed to support the intended business functions. System performance is
compared to performance objectives established during the planning phase. Implementation
includes user notification, user training, installation of hardware, installation of software onto
production computers, and integration of the system into daily work processes. This phase
continues until the system is operating in production in accordance with the defined user
requirements.
The system operation is ongoing. The system is monitored for continued performance in
accordance with user requirements and needed system modifications are incorporated. Operations
continue as long as the system can be effectively adapted to respond to the organization’s needs.
When modifications or changes are identified, the system may reenter the planning phase.
10
SOURCE CODE
Note:
• Allow the administrator to delete an enrollment, edit the name and course of a candidate.
SOLUTION:
CIMS_CREATE_DATABASE.PY
conn=sql.connect(host='localhost',user='root',passwd='manager')
if conn.is_connected():
print("Successfully Connected")
c1=conn.cursor()
CIMS_CREATE_TABLES.PY
11
import mysql.connector as sql
conn=sql.connect(host='localhost',user='root',passwd='manager',database
='cims')
if conn.is_connected():
print("Successfully Connected")
c1=conn.cursor()
CIMS_MENU.PY
conn=sql.connect(host='localhost',user='root',passwd='manager',database
='cims')
#if conn.is_connected():
# print("Successfully Connected")
c1=conn.cursor()
Management System")
print(" ")
print("4. Exit")
12
choice=int(input("Enter the Choice - "))
if choice==1:
if v_course=='JAVA':
v_course='JAVA'
elif v_course=='Python':
v_course='Python'
elif v_course=='C':
v_course='C'
elif v_course=='BASIC':
v_course='BASIC'
elif v_course=='HTML':
v_course='HTML'
c1.execute(V_SQL_Insert)
print(" ")
Mr.",v_candidatename,". Congrats!!!")
conn.commit()
print(" ")
uname=input("Enter Username:")
passwd=input("Enter Password:")
u_name='abc'
pass_wd='123'
print("
Password Accepted")
print(" ")
choose ?"))
if option==1:
candidate to be removed:"))
str(change_adm_no)
c1.execute(V_SQL_Insert)
print("")
print("
Successfully removed")
conn.commit()
if option==2:
14
change_adm_no=int(input("Enter the admission number of the
c1.execute(V_SQL_Insert)
print("")
print("
Successfully edited")
conn.commit()
if option==3:
if change_course=='JAVA':
change_course='JAVA'
elif change_course=='Python':
change_course='Python'
elif change_course=='C':
change_course='C'
elif change_course=='BASIC':
change_course='BASIC'
elif change_course=='HTML':
change_course='HTML'
print("")
print("
Successfully modified")
conn.commit()
else:
if choice==3:
data=c1.fetchall()
print("
print("
print("
print("
print(" ")
print(" ")
if choice==4:
16
OUTPUTS
(Ctrl+Click the link to go to presentation)
17
18
19
(After enrolling 3 candidates)
20
TESTING
TESTING METHODS
Software testing methods are traditionally divided into black box testing and white box
testing. These two approaches are used to describe the point of view that a test engineer takes
when designing test cases.
Black box testing treats the software as a "black box," without any knowledge of internal
implementation. Black box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing
and specification-based testing.
SPECIFICATION-BASED TESTING
21
Specification-based testing aims to test the functionality of software according to the
applicable requirements. Thus, the tester inputs data into, and only sees the output from, the test
object. This level of testing usually requires thorough test cases to be provided to the tester, who
then can simply verify that for a given input, the output value (or behaviour), either "is" or "is not"
the same as the expected value specified in the test case. Specification-based testing is necessary,
but it is insufficient to guard against certain risks
The black box tester has no "bonds" with the code, and a tester's perception is very simple:
a code must have bugs. Using the principle, "Ask and you shall receive," black box testers find
bugs where programmers don't. But, on the other hand, black box testing has been said to be "like
a walk in a dark labyrinth without a flashlight," because the tester doesn't know how the software
being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many test cases to check
something that can be tested by only one test case, and/or (2) some parts of the back end are not
tested at all. Therefore, black box testing has the advantage of "an unaffiliated opinion," on the one
hand, and the disadvantage of "blind exploring," on the other.
White box testing, by contrast to black box testing, is when the tester has access to the
internal data structures and algorithms (and the code that implement these)
22
• fault injection methods.
• mutation testing methods.
• static testing - White box testing includes all static testing.
White box testing methods can also be used to evaluate the completeness of a test suite
that was created with black box testing methods. This allows the software team to examine parts
of a system that are rarely tested and ensures that the most important function points have been
tested.
23
INSTALLATION PROCESS
24
HARDWARE AND SOFTWARE REQUIREMENTS
AMD ATHALON
SOFTWARE REQUIREMENTS:
• Windows OS
• Python
25
BIBLIOGRAPHY
***
26