CASE Tools 2

CASE Tools Concepts and Its Applications
Unit 2
Dr. Maharasan.K.S
Department of Computer Applications
KG CAS
Unit II
 Solving the problem statement
 DFD for Payroll System
 Presentation Diagram for Payroll System & Schematics of the Model
 User Interface Design - Forms
 Screens-Menu Screens
 Screens-Data Entry Screens
 Report Output Format-Utilities
 How to use the tools in Ubridge
 Installation of Ubridge Synthesis
 Getting Ubridge to work
 Setup-Assign-House keep
 Ubridge Page
SDLC
• The Software Development Life Cycle

(SDLC), or System Development Life Cycle in
systems engineering, information systems and
software engineering, is the entire process of
formal, logical steps taken to develop a
software product.
• The concept generally refers to computer or
information systems.
SDLC
SDLC Phases:
• Problem Definition.
• Program Design.
• Coding.
• Debugging.
• Testing.
• Documentation.
• Maintenance.
• Extension and Redesign
SDLC
Problem Definition: SDLC
 Problem definition is the basic and primary step
of software development life cycle.
 It includes the goal of system analysis and to
determine where the problem is in an attempt to
fix the system.
 This step involves "breaking down" the system in
different pieces to analyze the situation.
 Requirements Gathering sometimes requires
individuals/teams from client as well as service
provider sides to get detailed and accurate
requirements.
Program Design SDLC
• The design stage takes as its initial input the

requirements identified in the approved
requirements document.
• Design elements describe the desired software
features in detail, and generally include functional
hierarchy diagrams, screen layout diagrams,
tables of business rules, business process
diagrams, pseudo code, and a complete entity-
relationship diagram with a full data dictionary.
Coding SDLC
• Modular and subsystem programming code

will be accomplished during this stage.
• Coding includes the application of various
logic and internal work done by various
specialists.
• This stage is intermingled with the next in that
individual modules will need testing before
integration to the main project.
Debugging SDLC
 Debugging is the process of removing the errors that
occurs during the coding part.
 Debugging is essential for this stage establishes the
platform for further stages of development.
Testing
 The code is tested at various levels in software testing.
 Unit, system and user acceptance testing’s are often
performed.
 This is a grey area as many different opinions exist as
to what the stages of testing are and how much if any
iteration occurs.
Documentation SDLC
• Documentation is the process of writing down

every stages and each and every details of the
process of life cycle development so that
anyone who follows this process may be able
to do it in the real sense.
• Documenting the internal design of software
for the purpose of future maintenance and
enhancement is done throughout development.
Maintenance SDLC
 Maintaining the system is an important aspect of
SDLC.
 As key personnel change positions in the organization,
new changes will be implemented, which will require
system updates.
 Maintenance is the process of keeping the software in
its fully functional form and see to that nothing goes
wrong.
 Maintaining and enhancing software to cope with
newly discovered problems or new requirements can
take far more time than the initial development of the
software
Extension and Redesign SDLC
• This is the last step of system design where

there is always scope for extension and
redesign whenever required.
• This stage allows for the extension of any part
for the advancement of the software or so that
the developed software does not become
useless.
• This stage allows further designing and
following all the steps again.
Different types of SDLC models SDLC
 1.Waterfall Model
 2.Software Prototyping
 3.Joint Applications Design (JAD)
 4.Rapid Application Development (RAD)
 5.Extreme Programming (XP)
 6.Prototyping and RAD.
 7.Spiral Model
 8.Agile Model
 9.End-user development
 and many more
Sample
Pay Roll Processing System
Sample
Sample
Sample
Sample
Sample
Sample
Sample
Pay Roll Processing System - Forms
• Advantages of Forms
• User Interface
• Characteristics of User Interfaces
• Graphical User Interface
• GUI Guidelines
• Advantages
• Samples
• UX Design
Sample
Pay Roll Processing System - Forms
Tentative Menu screens
• 1. MAIN_MENU SCREEN
• 2. MASTER_MENU SCREEN
• 3. PIS SCREEN
• 4. LOAN SCREEN
• 5. GOVT SCREEN
• 6. TRANSACTION_MENU SCREEN
• 7. NO.of.DAYS SCREEN
• 8. EXIT MENU SCREEN
• 9. REPORT MENU SCREEN
• 10. PAYSLIP SCREEEN
• 11. UTILITIES SCREEN
• 12. BACKUP SCREEN
• 13. PASSWORD SCREEN
Problem Statement
 It is a statement of a current issue or problem that requires
timely action to improve the situation.
 Concisely explains the barrier the current problem places
between a functional process and/or product and the current
(problematic) state of affairs.
 Completely objective, focusing only on the facts of the
problem and leaving out any subjective opinions.
 What, who, when, where and why queries will be answered
to create the structure for the problem statement.
 Makes it easier to create , read, and makes the problem at
hand more comprehensible and therefore solvable.
 The problem statement, in addition to defining a pressing
issue, is a lead-in to a proposal of a timely, effective solution.
Problem Statement
• How to solve a problem statement
• It is a tool used to gain support and approval of the project
from management and stakeholders.
• It must be accurate and clearly written.
• Key elements to be kept in mind while crafting a problem
statement.
– Describe how things should work.
– Explain the problem and state why it matters.
– Explain your problem's financial costs.
– Back up your claims.
– Propose a solution.
– Explain the benefits of your proposed solution(s).
– Conclude by summarizing the problem and solution.
• Reason : To have a positive impact on the outcome of the
project
Crafting a Problem Statement
1. Describe how things should work
• To begin, you'll want to provide some context that will make it
easier to understand the problem. Start by explaining how
this particular process should work. Concisely describe how
the process would function if the current problem didn't exist
before mentioning the problem, keeping the end-user in
mind. For example, let's say that you have an idea of how to
increase efficiency in a process to maximize the best use of
resources. You might begin by describing a theoretical
situation in which the system is more efficient and working
toward your proposal from there, always keeping in mind
who, what, when, where and why to keep yourself on track.
2. Explain the problem and state why it matters
• The problem statement should address not only what the
problem is, but why it's a problem and why it's important to
solve it. This will wrap the other 'W' questions in organically,
in most cases. For example: Why should we fix this problem?
Because it affects the efficiency of departments X, Y and Z,
wasting resources and driving prices up for consumers. This
addresses what the problem is, who is affected and why the
problem should be fixed. You may also consider including
what attempts have already been made to solve the problem
and why they didn't work out. As concisely as possible,
explain everything you know about the current problem.
3. Explain your problem's financial costs
When you state the problem to decision-makers, you'll want to
explain the costs of not fixing it. Seeing as money is the language
in which businesspeople speak, it's easiest to frame the problem
and proposed solution in terms of financial costs. For example, if
the problem is actively costing unnecessary money, preventing
the company from making more money or damaging the
company's public image (indirectly costing money) make sure
you explain it specifically and clearly in terms they understand.
Try to pinpoint exact dollar amounts for the problem's cost.
4. Back up your claims
• Once you claim the problem is costing the company money,
you must be prepared to support your claims with evidence. If
you neglect this step, you may not be taken seriously. Do your
research, cite your sources and have the data ready to
present.
5. Propose a solution
• The problem statement should describe your proposed
solution(s) to the problem. At this point, you won't be focused
on finding a single solution, but you should have a solid grasp
on the causes of the problem and be prepared to propose
practical approaches to understanding and remedying it. State
your objectives by suggesting well-thought-out plans for
attacking the problem.
• 6. Explain the benefits of your proposed solution(s)
• Now, you've described an ideal scenario in which the problem
doesn't exist. You've pointed out the problem, explaining the
ramifications of choosing not to fix it (using dollars and solid
data) and proposed some realistic approaches to finding a
solution. Now is a very good time to demonstrate why this
solution will work, again focusing on efficiency and the
financial impact of your solution. Address what expenses the
solution will decrease, how this solution will free up revenue
streams and what intangible benefits, such as increased client
satisfaction, your solution will bring. This should all fit into a
single short paragraph.
• 7. Conclude by summarizing the problem and solution
• Now you'll move onto your conclusion. This should consist of
the problem, why it needs to be fixed and a summarized
argument of why your solution is the best answer to the
problem.
• Following this format will help all parties who read it to
understand the problem and be open to considering the best
solution.

CASE Tools 2

Uploaded by

Copyright:

Available Formats

CASE Tools 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CASE Tools 2

Uploaded by

Copyright:

Available Formats

CASE Tools Concepts and Its Applications

• The Software Development Life Cycle

• The design stage takes as its initial input the

• Modular and subsystem programming code

• Documentation is the process of writing down

• This is the last step of system design where

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.