Chapter 7

What is process modeling?

 Process Modeling: Graphically represent the processes that capture, manipulate,

store, and distribute data between a system and its environment and among
system components.

 Utilize information gathered during requirements determination.

 Processes and data structures are modeled.

Our project is object oriented so we used sequence diagram as a process modeling

tool.
chapter 8 possible questions
logical modeling

 Data flow diagrams do not show the logic inside the processes.
 Logic modeling involves representing internal structure and functionality of
processes depicted on a DFD.
 Logic modeling can also be used to show when processes on a DFD occur.
As a solution we do
 Structured English representation of process logic.
 Decision Tables representation.
 Sequence diagram.
 Activity diagram.
So in our project we used a sequence diagram in which we showed the logic inside the
process and representing of internal structure and functionality
Chapter 12 possible questions:

System & Organization Implementation

System implementation:
 Six major System activities:
1. Coding
2. Testing
3. Installation
4. Documentation
5. Training
6. Support

 Purpose:
 To convert final physical system specifications into working and reliable
software.
 To document work that has been done.
 To provide help for current and future users.
Steps:

 Coding
 Physical design specifications are turned into working computer code.
 Testing
 Tests are performed using various strategies.
 Testing performed in parallel with coding.
 Installation
 The current system is replaced by new system.
 User Training
 Application-specific.
 General for operating system and off-the-shelf software.

In terms of our project, we first started coding, in which we turned physical design
specification into working computer code. For coding we used PHP, XHTML, CSS and
JavaScript. After finishing the coding part, we did unit , integration , and system
testing. The purpose of testing is to confirm that the system satisfies the
requirements. In unit testing , we tested each module alone in an attempt to
discover any errors in its code. After finishing unit testing, we moved to integration
testing in which we brought together all of the modules that a program comprises
for testing purposes. The last step in the testing section that we did is system testing
, in which we brought together all of the programs that a system comprises for
testing purposes.We also performed some testcases. One example of a testcase:
Testcase: T1 testdata:ID123 password:123 expected output: A message will be
shown
saying ID Or Password is Incorrect, Please try again Result: Message is shown saying
id or password is incorrect. Pass.
After finishing testing by developer and analysts. We moved into user testing. We
did two types of user testing , Alpha testing: user testing of a completed information
system using simulated data.Beta testing: user testing of a completed information
system using real data in the real user environment. Installation: the organizational
process of changing over from the current information system to a new one. There
are four types of installation: Direct Installation.
Parallel Installation.
Single-location installation.
Phased Installation.
In our project we did a Direct installation: changing over from the old system to a
new one by turning off the old system when the new system is turned on.
In terms of support. We will be having an internet based support since our system is
web based system. We will be having online forms to be filled by users, also online
chatting for any problems with the users
 Chapter 13 possible questions

Maintenance is the longest phase in the SDLC. The maintenance phase of the SDLC
is basically of subset of the activities of the entire development process. The
deliverables and outcomes from the process are the development of a new version
of the software and new versions of all design documents created or modified during
the maintenance effort. Maintenance: changes made to a system to fix or enhance
its functionality. Four major activities:
Obtaining maintenance requests.
Transforming requests into changes.
Designing changes.
Implementing changes.

There are different types of maintains. The first Maintenance type we are expected to
perform on our project is Corrective maintenance, in which we make changes to our
system to repair flaws in its design, coding, or implementation. Second one we are expected
to do is perfective maintenance in which we will do changes to our system to add new
features or to improve performance. Another type is Preventive maintenance: in which
changes made to our system to avoid possible future problems. Our organizational structure
in terms of maintenance is combined, which means developers also maintain the system.
What we will do to measure maintenance effectiveness is that we will do a Mean time
between failures (MTBF) measurement, which is a measurement of error occurrences that
can be tracked over time to indicate the quality of a system. To control maintenance
requests we will prioritize requests based on type and urgency of request. Since we have a
website we do a website maintenance. First the page which is under maintenance can be
locked , then Check for broken links and do HTML Validation, which is pages should be
processed by a code validation routine before publication.
UML 2:
UML has the following diagram types:
Use-case diagrams
Static-structure diagrams:
Object diagrams
Class diagrams
Interaction diagrams:
Sequence diagrams
Collaboration diagrams

Implementation diagrams:
Component diagrams
Deployment diagrams