Home Work-11

1. what is the purpose of creating a logical process model and then a physical process
model?

The basic purpose of creation of logical process models first and physical model next is to

concentrate mainly on the business requirements of the system (Dennis et al, 2012). When

reading a logical process model, a person may not be able to specifically distinguish

whether a process is computerized or manual. These physical details are explained during

the design phase, while these logical models are transfigured into physical models. Also

physical models help analysts to study implementation details of a system and how the

final system will work.

Logical process models specify constraints on the access to data and identify who is in

control of data at different nodes in the dataflow network that is designed. Hence, data

abstraction is implemented, and data is protected from unwanted access.

4. What is a human–machine boundary?

- Human-machine boundary is a line drawn on the model to separate human action from

automated processes.
5. Why is using a top-down modular approach useful in program design?

Top-down design (sometimes called ‘stepwise refinement’) is a term used to describe how

a complex problem is broken down into modules. Those modules are then broken down

into sub-modules. Each sub-module is then broken down further and further, until the sub-

modules do just one task and are simple enough to program. Instead of writing one big

program, the program is split into self-contained ‘modules’ of code. Modules are

sometimes called ‘procedures‘ or ‘functions’. This approach has many advantages!1.

Splitting up a problem into modules helps get the job done more efficiently because

modules of code can be worked on at the same time by different programmers.2. Splitting

up a problem into modules helps a team of programmers work more efficiently because

easier modules can be given to less experienced programmers while the harder ones can be

given to more experienced ones.3. Splitting up a problem into modules helps program

testing because it is easier to debug lots of smaller self-contained modules than one big

program.4. Splitting up a problem into modules helps program readability because it is

easier to follow what is going on in smaller modules than a big program.5. Splitting up a

problem into modules improves a company’s efficiency because self-contained modules

can be re-used. They can be put into a library of modules. When a module is needed to

display some values, for example, you don’t need to get the programmers to write and test

a module for this again. You just re-use a module from the library. Over time, this will save

a company a lot of time and money.6. Splitting up a problem into modules improves a

Project Manager’s ability to monitor the progress of a program. Modules can be ‘ticked off

the list’ as they are done and this will demonstrate some progress. This is far harder for a
Project Manager to do if the program has not been split up into modules.7. Splitting up a

problem into modules is good for future program maintenance. If a program needs to be

changed for any reason, it may be possible simply to remove one module of code a

6. Describe the primary deliverable produced during program design.

What does it include and how is it used?

- At the end of program design, the project team compiles the program design

document, including all of the structure charts and program specifications that will be

used to implement the system. The program design is used by programmers to write

code.