Practical1

AIM: Project Definition search and customer meetings, Submit current semester
project proposal.

CONTEXT

Cyber Cafe monitoring system is a professional monitoring and management system for
cyber cafe.
It consists of the centralized system which will remotely manage all the computers in
cyber cafe.

INFORMATION

The present system was an elementary one. The employee would keep a
notebook to manage all the terminals. The problems prevailing in the present system are
as follows:

 Inconsistency
 Login and log off time monitoring
 Duration of on and off time
 Internet traffic
 Security is not maintained
OBJECTIVES

The main objectives of the system are to put the newly available
technology in securing the employees of the lab for economic effective and increase
performance of the system. An employee can monitor and manage the entire site from all
relevant aspects, logging on customers remotely, executing wide range of actions on one
or more or all of the terminals at once remotely.

FUNCTIONS

It includes monitoring and management system. It includes following

features:

 States of clients (Computer) i.e. log in time, current users, elapsed time, etc.
 Any client’s session can be terminated as and required.
 Enable/Disable of client computer can be done from the server end (using IP
address).
 Chat with any computer (client) can be done.
 Security – password, privileges.
 Monitoring of individual client.
 Context of individual terminal.
PERFORMANCE

The newly system developed would increase the efficiency of the lab.
The concept of the client and server makes safety advancements, it also allows for an
efficient centralized management of the entire system.

 Control and checking on all the activities of each terminal.

 Monitoring the system while it is on/off.
 Better means of solving faults and problems.
 Controlled and secured access is achieved.

PROBLEM DECOMPOSITION

 We will use login for secured access of each user.

 Connection (to access net) to the server is made only after the successful login.
 Database is maintained to store the login time of individual user.
 Only server has the rights to terminate any terminal (client) to control the access.
 Client is not connected to server until user logs in which reduces the network
traffic.
 Practical2

AIM: Study of different software engineering models.

 Waterfall model, Prototype model, Incremental model, Spiral model and RAD
model.
 Student should write description about above model and also comparison of it.
 At the end of practical student should write which model is selected for current
semester project and also justification for it.

Incremental model
Developing systems through incremental release requires first providing essential
operating functions, then providing system users with improved and more capable
versions of a system at regular intervals .This model combines the classic software life
cycle with iterative enhancement at the level of system development organization. It also
supports a strategy to 7 periodically distribute software maintenance updates and services
to dispersed user communities.
This in turn accommodates the provision of standard software maintenance contracts. It is
therefore a popular model of software evolution used by many commercial software firms
and system vendors. This approach has also been extended through the use of software
prototyping tools and techniques (described later), which more directly provide support
for incremental development and iterative release for early and ongoing user feedback
and evaluation

The iteration involves the redesign and implementation of a task from project control list,
and the analysis of the current version of the system. The goal for the design and
implementation of any iteration is to be simple, straightforward, and modular, supporting
redesign at that stage or as a task added to the project control list. The code can, in some
cases, represent the major source of documentation of the system. The analysis of
iteration is based upon user feedback, and the program analysis facilities available. It
involves analysis of the structure, modularity, usability, reliability, efficiency, and
achievement of goals. The project control list is modified in light of the analysis results.

Guidelines that drive the implementation and analysis include:

 Any difficulty in design, coding and testing a modification should signal the need
for redesign or re-coding.
 Modifications should fit easily into isolated and easy-to-find modules. If they do
not, some redesign is needed.
 Modifications to tables should be especially easy to make. If any table
modification is not quickly and easily done, redesign is indicated.
 Modifications should become easier to make as the iterations progress. If they are
not, there is a basic problem such as a design flaw or a proliferation of patches.
  Patches should normally be allowed to exist for only one or two iterations.
Patches may be necessary to avoid redesigning during an implementation phase.
 The existing implementation should be analyzed frequently to determine how well
it measures up to project goals.
 Program analysis facilities should be used whenever available to aid in the
analysis of partial implementations.
 User reaction should be solicited and analyzed for indications of deficiencies in
the current implementation.

JUSTIFICATION

In Waterfall model, it is a sequential model i.e. once the requirement analysis

is over and we enter the next phase requirement analysis can not be done and similarly
for other cases also once we enter the next phase we cannot re-enter the previous case. So
this model can be implemented if and only if we are confident in all the phase’s
completion. Moreover, customer can increase or decrease the requirements any time. So
this model is not feasible, while in incremental model we start the development with
some initial (basic) requirements of the customer, and requirements can be added
afterwards.
Prototype model is used when the system to be developed is unknown to us,
while the system (Cyber café monitoring system) we are developing is known to us so
prototype model is also not suitable.
Spiral model is used if there is a risk of technology and also it is used for day
by day changing requirements. As there is no such condition in this system so this model
is also not suitable.
 Practical3

AIM: Study Software Requirement engineering. Student should include SRS document
for current semester project.

SRS (Software requirement specification)

Name of the System: Café monitoring system

ASSUMPTION:
1. User’s are already registered.

Requirement 1: Authentication
Req1.1: Enter the id and password of user.
INPUT: userid and password (external).
OUTPUT: Validate the user according to authority.
Req1.2: Terminate the customer session when credit limit or duration of
session specified for user is less than RS. 10 or 5mins respectively.
Requirement 2: Show information
Req 2.1: User information
INPUT: userid and password (internal)
OUTPUT: username, email, phone no., total time left,
address.
Req 2.2: Account information
Input: memerid (external).
Output: name, date, access time, amount.

Requirement 3: Registration of user (only by admin)

INPUT: userid, password, phone no., email, scheme, address.
(external).
OUTPUT: Registration status.

Requirement 4: Delete user (only by admin).

INPUT: username and password (external).
OUTPUT: Deletion status.
Requirement 5: Server can monitor the clients.
Req5.1: Enable/Disable client from server.
INPUT: client name (External).
OUTPUT: client status.

Req5.2: Chatting between server and client (by server only).

INPUT: client machine name (internal).
OUTPUT: message.

Req 5.3: Display the configuration of each computer.

Req 5.4: Remote Shutdown/restart the client machine.

Requirement 6: View status of each computer (free/occupied), connected or not

connected.

Requirement 7: Bill generation at the end of the session. And also see the bill details
of each customer

Requirement 8: Main admin window shows logged member/user, duration, amount,

remaining time, pc no.

Requirement 9: Schemes maintenance.

Req 9.1: Add new schemes when required
Input: new schemes (external).
Output: addition status.
Req 9.2: Change the schemes already present.
Input: schemes to be updated (external).
Output: updating status.
Requirement 10: Graph showing time period Vs computer

Requirement 11: Members/users are allowed to see member id, time left below the
window as status bar. And provide logout option to each user.

Requirement 12: Generate coupons with unique userid and password for visitors.
SRS (Software requirement specification)(revised)

Name of the System: Cyber Café monitoring system

Requirement 1: Authentication

Req1.1: Enter the id and password of user.

INPUT: userid and password (external).
OUTPUT: Validate the user according to authority.

Req1.2: Terminate the customer session when credit limit or duration of

session specified for user is less than RS. 10 or 5mins
respectively.

Requirement 2: User Management

Req 2.1: Show information

Req 2.1.1: User information

INPUT: userid and password (internal)
OUTPUT: username, email, phone no., total time
left, address.

Req 2.1.2: Account information

INPUT: memerid (external).
OUTPUT: name, date, access time, amount.

Req 2.1.3: Members/users are allowed to see member id, time

left below the window as status bar. And provide
logout option to each user.

Req 2.2: Registration of user (only by admin)

INPUT: userid, password, phone no., email, scheme, address.
(external).
OUTPUT: Registration status
Req 2.3: Delete user (only by admin).
INPUT: username and password (external).
 OUTPUT: Deletion status.

Requirement 3: Client management.

Req3.1: Enable/Disable client from server.
INPUT: client name (External).
OUTPUT: client status.

Req3.2: Chatting between server and client (by server only).

INPUT: client machine name (internal).
OUTPUT: message.

Req 3.3: Display the configuration of each computer.

Req 3.4: Remote Shutdown/restart the client machine.

Req 3.5: View status of each computer (free/occupied), connected or not

connected.

Requirement 4: Schemes maintenance.

Req 4.1: Add new schemes when required
Input: new schemes (external).
Output: addition status.

Req 4.2: Change the schemes already present.

Input: schemes to be updated (external).
Output: updating status.

Requirement 5: Server management

Req 5.1: Bill generation at the end of the session. And also see the bill
details of each customer

Req 5.2: Main admin window shows logged member/user, duration,

amount, remaining, time, pc no.

Req 5.3: Graph showing time period Vs computer

 Req 5.4: Generate coupons with unique userid and password for visitors

Practical4

AIM: Study Software project management planning. Student should write SPMP
document for current semester project.

Gantt Chart
T1
( Project
Definition)

T2 (Req.
Gathering)

T3 (System
Requirement
Specification)
T4 (DB
design)
T6 (coding)
T5 (UI
design)

T7 (System
Testing and
debuging)

T15
(Deployment)
 Practical5

AIM: Study of different Software Cost Estimation models.

 Student should study size oriented matrices such as LOC and FP.
 Student should study COCOMO
 Students should estimate current semester project through above model.

External Input:
Req1.1 Req2.1.2 Req2.2
Req2.3 Req3.1 Req4.1
Req4.2

External Output:
Req3.1 Req3.2

No. of Inquiries:
 Member information
 Status
 Profit / Loss inquiry

No. of External Files:

 database

No. of External Interfaces:

 Client machine
 Printer
Calculation of Function Point (FP):

No. of External Inputs: 7

No. of External Outputs: 2
No. of External Inquiries: 3
No. of External Files: 1
No. of External Interfaces: 2

UFP = 7*3+2*5+3*3+1*7+2*10
=67
UFP = 67

F1: Does the system require reliable backup & recovery? 5

F2: Are data communications required? 5
F3: Are there distributed processing functions? 1
F4: Is performance critical? 3
F5: Will the system run in an existing, heavily utilized operational 0
environment?
F6: Does the system require online data entry? 2
F7: Does the online data entry require the input transaction to be 3
built over multiple screens or operation?
F8: Are the master files updated online? 4

F9: Are the inputs, outputs, files or inquiries complex? 1

F10: Is the internal processing complex? 1

F11: Is the code designed to be reusable? 2
F12: Are the conversion and installation included in design? 1

F13: Is the system design for multiple installations in different 2

organizations?
F14: Is the application designed to facilitate change and ease of use 4
by the user?
FP = 67*(0.65+0.01*(34))
FP = 66.33

COCOMO (Constructive Cost estimation Model)

1 FP = 32 LOC in VISUAL BASIC

so, 66.33 = 2122 LOC
so, Approximately 2 KLOC

Efforts = 3.6  (2)1.2

= 8.27
= 8 PM

Tdev = 2.5  (5)0.32

= 4.18 months
 Practical6

AIM: Design SA/SD for current semester project. It includes Requirement

specification, DFD with data dictionary and Structure chart for current semester
project.

DATAFLOW DIAGRAM

LEVEL 0(CONTEXT LEVEL)

LEVEL 1
Level 1 (revised)
Level 2 DFD for non-members
Level 2 DFD for members
 DATA DICTIONARY

1) Table name: login_master

Primary key: userid
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

Userid Varchar2 20 Primary key. Member’s id/coupons
for non-members
Password Varchar2 20 Should not be null Member’s password

2) Table name: mem_master

Primary key: memid
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAIN DESCRIPTION

T
Memid Varchar2 10 Provide unique id to each
Primary key.
member
address Varchar2 10 Stores address of each member
Phone Number 10 Stores phone number of each
member
Email Varchar2 20 Stores email id of each member
Date Date/time 8 Stores registration date
time Date/time 8 Stores total time left for surfing
 3) Table name: coupon_master
Primary key: coupid
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

Coupid Varchar2 10 Provides unique coupon for
Primary key.
non-members
Time Number 8 Stores the total time provided
by coupon(in hours)
Days Number 4 Stores the total days for
expiring coupon

4) Table name: account_master

Primary key: {id, logindate, logintime}
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

Id Varchar2 20 Primary key. Stores the id of user
Logindate Date/time 8 Primary key Stores the login date of user
Logintime Date/time 8 Primary key Stores the login time of user
Logofftime Date/time 8 (Logoff-login) time Stores the current balance of
should not exceed user
the valid time
remaining for user

5) Table name: scheme1_master

Primary key: schemeid
Foreign key: null References:
 FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION
Schemeid Varchar2 20 Primary key Stores the id of scheme
Time Number 10 Stores the total time provided
by scheme (in hours)
Days Number 10 Stores the total days for
expiring the scheme
Rupees Number 4 Stores the amount for the
schemes

6) Table name: scheme_master

Primary key: {schemeid, memid}
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

Schemeid Varchar2 10 Primary key Stores the id of schemes
Memid Varchar2 10 Primary key Stores the id of member

DATA DICTIONARY (revised)

1) Table name: mem_master
Primary key: mem_id
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

mem_id Varchar2 20 Provide unique id to each
Primary key.
member
Address1 Varchar2 10 Stores address of each member
Phone1 Number 10 Stores phone number of each
member
Email1 Varchar2 20 Stores email id of each
member
Date1 Date/time 8 Stores registration date
Time1 Varchar2 8 Stores total time left for surfing
Name1 Varchar2 20 Store the name of the member
Scm_id1 Varchar2 20 Stores the id of the scheme
password Varchar2 20 Stores the member password

2) Table name: coupon_master

Primary key: coupid
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

Couponid Varchar2 10 Provides unique coupon for non-
Primary key.
members
price Number 8 Stores the total price of specific
coupon(according to hours)

3) Table name: account_master

Primary key: {id, logindate, logintime}
Foreign key: References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

Id Varchar2 20 Primary key. Stores the id of user
Logindate Date/time 8 Primary key Stores the login date of user
Logintime Varchar2 8 Primary key Stores the login time of user
Logofftime Varchar2 8 (Logoff-login) time Stores the current balance of
should not exceed user
the valid time
remaining for user
 4) Table name: scheme1_master
Primary key: scm_id
Foreign key: null References:

FIELDNAME DATATYPE SIZE CONSTRAINT DESCRIPTION

Scm_id1 Varchar2 20 Primary key Stores the id of scheme
Time Varchar2 10 Stores the total time provided
by scheme (in hours)
Days Number 10 Stores the total days for
expiring the scheme
Ruppees Number 4 Stores the amount for the
schemes

STRUCTURE CHART

ADMIN

REGISTER RECHARGE COUPON

NEW USER ACCOUNT VISITOR

CLASS DIAGRAM
 Practical7

AIM: System Design using Object Oriented approach. Use case Diagram with
scenarios, Class Diagram and State Diagram for Current semester project.
STATE DIAGRAM

FOR USER
FOR ADMIN
FOR SERVER
USE CASE SCENARIO

1) Admin enter’s user name and password to login into the system.

2) Admin has some menu options to select ,like new user(register),recharge, member info
by clicking on member as it is shown with pc no, login time, elapsed hrs,amount of that
user, delete member, decide scheme,etc.

3) Now for registration admin enters the information about the member like name, id,
password, e-mail, address, and phone.

4) Then user has to select the scheme provided accordingly user is registered.

5) Admin also recharges the member account balance by providing different schemes.

6) User can login and start surfing.

7) Admin can delete member by entering memid and password.

8) Each level of user is given logout option.

USE – CASE DIAGRAM
 Practical8

AIM: System Design using Object Oriented approach. Collaboration Diagram,

Sequence Diagram and Activity Diagram for Current semester project.

ACTIVITY DIAGRAM
(ADMIN)

(USER)
SEQUENCE DIAGRAM
COLLABORATION DIAGRAM
 Practical9

AIM: Coding Standards and walk through

1) The project title must always be set to something meaningful as it is used in the
Windows task list and for message box captions when no default is supplied in the call to
the message box function.

2) A help file must be associated with all components. For application modules, help files
should describe key application features and operational instructions. For ActiveX
components, help files should describe component design goals, classes, methods,
properties and enums etc. to aid re-use by other developers.

3) The project icon should be set as it becomes the application icon when the project is
compiled.

4) The application start-up object must always be 'Sub Main' for standard EXE
components.

5) To ensure that all source files pertaining to a Visual Basic project are correctly
archived, all project source files must reside in the same folder as the Visual Basic project
file (.VBP).

6) The extension of designer files must match the Visual Basic default extension of '.dsr'.

7) Form filenames must use the Visual Basic default extension of '.frm.

8) The extension of module filenames must use the Visual Basic default extension of
'.bas'.

9) The scope for a module-level 'Const' declaration must always be explicitly declared
Public or Private as appropriate.

10) The "As" keyword must be used within a constant declaration to explicitly state the
data type of the declared constant.

11) Procedure return data types must not return arrays. Due to a known bug in Visual
Basic 6.0, when you use a function that returns an array as a parameter to the UBound or
LBound functions, the memory allocated for the array is not released thereby causing a
memory leak.
12) To aid code readability, all local variables must be declared at the head of a
procedure.

13) To ensure that procedures are easy to understand, test and maintain, 'If...Then'
statements must not be nested beyond three levels deep.

14) To reduce code complexity and improve code readability avoid nesting Select...Case
statements within other Case statement blocks. If the Case statement needs to perform
conditional or complex logic this is best delegated to another function.

15) The "Stop" statement should not be used during debugging as it may be accidentally
left within source code and cause the compiled application to terminate abruptly. The
"End" statement should be used instead if the application is indeed to terminate. If the
"Stop" statement was intended to highlight a problem during debugging, replace the
"Stop" statement with "Debug.Assert False".

16) Use of the "On Error GoTo 0" statement to switch off error trapping within a
procedure is not common practice and must be carefully considered before
implementation.

17) To achieve a consistent user interface, all forms must contain a control box.

18) keyboard navigation of the user interface.

19) The maximum number of controls per form must not exceed 50. Forms containing
large numbers of controls are perceive to be "busy" and not intuitive for users. Large
numbers of controls per form also consume resources and can lead to application failure
and should therefore be avoided.

20) Dialog 'OK' buttons must not be defined which contain an accelerator key e.g. '&OK'
must not be used whereas the caption 'OK' is allowed if the Default property is also set to
True.

21) Variant variables add additional overhead to execution which can degrade operational
performance and also prevents strict type checking. Declaration of variables 'As Variant'
must be avoided whenever possible.

22) Each time ReDim Preserve is used, the existing array must be copied to a new
memory location which can degrade operational performance if repeated often. If you
must use dynamic arrays, consider growing the array by larger increments so that ReDim
Preserve can be invoked less often. This can have a drastic effect on performance.
Alternatively, you may wish to consider the use of a collection under some
circumstances.
Practical10
AIM: Study of different Testing Tools with comparison

Functional Test Tools

Product Vendor Comments

.TEST Parasoft Unit-testing tool that automatically tests classes written on
Microsoft's .NET Framework without requiring developers to
write a single test scenario or stub.
AberroTest Aberro AberroTest is a functional test and verification product that
Software works at the user interface level.

Performance Test Tools

Product Vendor Comments
BugTimer BugStomper BugTimer was designed to streamline the entire process of
Software timing and documenting Performance Test results into one
Application. BugTimer is a timer application that records,
displays, saves, sorts, and prints Performance Test results.
DB DTM Utility for stress testing the server parts of information
Stress systems and applications, as well as DBMSs and servers
themselves.

Embedded Test Tools

Product Vendor Comments

Message Elvior Tests embedded software components - processes, subsystems,
Magic etc. With MessageMagic, one can test a certain component by
simulating its neighbour components. Contains tools for
visualization of messages traffic (also ASN.1 messages) between
the testable component and their simulated counterparts.
Reactis Reactive Generates comprehensive test suites from Simulink/Stateflow
Tester Systems models. The test suites exercise large portions of the software
under test while avoiding redundancy, thereby maximizing the
probability of finding defects within the time available for software
testing. The generated tests store model-generated outputs as
well as inputs so that Tester-generated test harnesses can
automatically check the correctness of source code
implementations of models.
 Practical11

AIM: Write test cases for Current semester project

Description of Main Menu

 ADMIN: It should contain various options performed by administrator only.

 SCHEME: It should provide different scheme.

 CONTROLS: It should be used to control client terminals.

 EXIT: It will exit from software.

 HELP: It will show a help page.

Graphical user interface:

1. Each control button should show tool tip associated with it.
2. Name of the window.
3. Text type face, size and format used through out the system were checked for
uniformity.
4. Grouping information is displayed appropriately.
5. Tab order should be maintained.
6. Alignment of each text box and equal spaces between the controls.
7. Each child form should fit into the MDI form.

Functional Test cases:

1. All menu functions and sub functions were verified for correctness.
2. A validation for all inputs was done.
3. Each menu function was tested, whether it invokes the corresponding
functionality properly.
4. Reset button will reset all setting.
5. Clear button will clear all values of control.
6. Check the number of users and authentication among the privileged user
should be their.
7. Registration should not allow special characters or digits in the name.
8. Browsing time should not exceed the left time in particular user account.
9. According to the use user left time should be decremented.
10. Status should be cleared as and when user logs in/out.
11. Controls of client terminal like shut down and restarts should be checked.
 Practical12

AIM: Differentiate different Software Quality Standards with context of application.

ISO, CMM, Six-Sigma standards

ISO
To lead and operate an organization successfully requires that it be managed in a
systematic and transparent manner. Managing an organization encompasses quality
management as one of the management disciplines.
In ISO 9001 for 1994, quality management was defined as a system, with twenty
elements of requirements that comprised that system. Each element referred to and
intertwined with other elements or sections of the standard. The quality management
standards of 1994 were based on the initial ISO 9000 series of standards issued in 1987,
which were the first management system standards developed by an international
committee under the authority of the International Organization for Standardization in
Geneva, Switzerland. Prior to the ISO 9000 Series of Standards, quality management
systems were based on Deming’s Fourteen Points, which are emphasized in the ISO
9001: 2000 standard.
Figure 1-1: ISO 9000 Standards: 1994 and 2000
1994 2000
ISO 9000—Quality management systems:
Fundamentals and vocabulary.
ISO 9001—Quality systems: Model for
quality assurance in design/development.
ISO 9001—Quality management systems:
Requirements.
ISO 9002—Quality systems: Model for
quality in production and installation.
ISO 9001, 9002, and 9003 have merged into a
single standard.
ISO 9003—Quality systems: Model for
quality assurance in final inspection and test.
ISO 9004—Quality management and quality ISO 9004—Quality management systems:
system elements: Guidelines. Guidelines for performance improvements.
ISO 9001:2000 is based upon eight quality management principles to enable the
organization to meet its quality objectives. These principles can be applied by top
management to direct the organization toward improved performance.

1. Customer Focus: Organizations depend on their customers, and need to understand

current and future customer needs. The key benefits of customer focus include increased
revenue and market share gained through flexible responses to opportunities.
 This principle was not very well focused in our project.
2. Leadership: Purpose and direction of the organization are determined by its leaders
who should cultivate an internal environment that allows people to become fully involved
in meeting the organization’s objectives. Miscommunication between levels of the
organization is minimized.
 This principle was very well focused.
3. Involvement of People: The full involvement of people at all levels allows their
abilities to be applied for the organization’s benefit. Once involved, people become
motivated and committed, contributing their creativity in furthering the organization’s
objectives.
 This principle was very well focused.

4. Process Approach: When activities and related resources are managed as a process,
the desired result can be achieved more efficiently. Having a process approach in place
results in lower costs and shorter cycle times through the effective use of resources.
 This principle was very well focused.

5. System Approach to Management: The organization can be more efficient and

effective in meeting its objectives when interrelated processes are identified, understood,
and managed as a system. Processes can be integrated and aligned to achieve the best
results, and allow an opportunity to focus effort on the key processes.
 This principle was very well focused.
6. Continual Improvement: Continual improvement should be integral to the
organization’s overall performance as a permanent objective. Improved performance
increases the organization’s capabilities and allows the flexibility to react quickly to
opportunities.
 This principle was very well focused.

7. Factual Approach to Decision Making: Focused and effective decisions are based on
the analysis and evaluation of data and information, which allows informed decisions.
The organization can more easily refer to factual records that document previous
effective decisions, which results in an increased ability to review, challenge, and change
opinions and decisions.
 This principle was very well focused.

8. Mutually Beneficial Supplier Relationships: Cultivating a mutually beneficial

relationship between the organization and its suppliers enables both to create value. Good
organization and supplier relationships optimize costs and resources, and result in
flexibility and speed of joint responses to changing market or customer needs and
expectations.
 This principle was not very well focused in our project.

SIX SIGMA :

 Team based, data driven system that improves processes and products through the
elimination of variation.
 Process observations are measured, analyzed, and visualized with advanced
statistical tools.
 Can be applied to any process.
 Addresses only the hard side of process improvements. No support of the soft side
organizational development.
  Broad based standardized training and certification system for Black Belts and
Green Belts.
 Project selection generally based on potential savings of $50,000 annually.
 Primary project outputs focused on process capability, product capability, and
quality.

Traditional Six Sigma methodology

 Define
 Measure
 Analyze
 Improve
 Control

Capability Maturity Model (CMM) broadly refers to a process improvement approach

that is based on a process model. CMM also refers specifically to the first such model,
developed by the Software Engineering Institute (SEI) in the mid-1980s, as well as the
family of process models that followed. A process model is a structured collection of
practices that describe the characteristics of effective processes; the practices included are
those proven by experience to be effective
The Capability Maturity Model can be used to assess an organization against a scale of
five process maturity levels. Each level ranks the organization according to its
standardization of processes in the subject area being assessed. The subject areas can be
as diverse as software engineering, systems engineering, project management, risk
management, system acquisition, information technology (IT) services and personnel
management.
 Practical13
AIM: Study of CASE Tools. Use Advance Features like Re-engineering and reverse
engineering with CASE Tool.

What is case?

Case is computer aided software engineering tools assist software engineering managers
and practitioners in every activity associated with the software process. They automate
project management activities; manage all work products produced throughout the
process, and assist engineers in their analysis, design, coding and test work. Case tools
can be integrated with in a sophisticated environment.

REVERSE ENGINEERING:

The term reverse engineering has its origin in the hardware world. A company dissembles
a competitive hardware product in an effort to understand its competitor’s design and
manufacturing “secrets”. These secrets could be easily understood if the competitor’s
design and manufacturing specifications were obtained. But these documents are
proprietary and unavailable to the company doing the reverse engineering. Reverse
engineering tools extract data, architectural and procedural design information from an
existing program.
ELDEAN ESS-MODEL

This tool allows generating a class diagram and also the information of the attributes used
from a .java file.
 Diagram Back to overview
Package: Default
Clock class
Inherits from: Applet
Implements: Runnable
Attributes
Name Type Visibility
timer Thread private
lastxs int private
lastys int private
lastxm int private
lastym int private
lastxh int private
lastyh int private
formatter SimpleDateFormat private
lastdate String private
clockFaceFont Font private
currentDate Date private
handColor Color private
numberColor Color private
xcenter int private

Operations
Name Parameters Returns Visibility
init public
update Graphics g public

paint Graphics g public

start public
stop public
run public
getAppletInfo String public
getParameterInfo String[][] public
CAVAJ JAVA DECOMPILER

Cavaj is a freeware utility that reconstructs java source code from CLASS files.
You can browse the reconstructed source code with the Class View for instant
access to methods and fields.
Enterprise Architecture

Enterprise Architect combines the power of the latest UML 2.1 specification with a high
performance, intuitive interface, to bring advanced modeling to the desktop, and to the
complete development and implementation team. With a great feature set and
unsurpassed value for money, EA can outfit your whole team, including analysts, testers,
project managers, quality control staff, deployment team and more, for a fraction of the
cost of some competing products.