Table of Contents………………………..

Page 1

Question 1

1. Print chart.........................................................................................2
2. Flowchart......................................................3&4
3. Pseundocode………………………………………..5,6, &7
Question 2
4. Hierarchal Diagram ...................................................................8
5. Pseudocode.........................................................................9,10&11
6. Pseudocode...........................................................................................12,13 & 14
Question 3
7. Rules for Creating and Naming Variables.........................................................15
8. Flowchart..................................................................................................16
9. Hierarchy Chart.........................................................................................17
10. The importance of Project Management, Feasibility Assessment, Data and
Information Gathering Techniques, and documentation in Software Development
Life Cycle. .................................................................................18, 19 ,20 ,21 ,&22
11. Reference…………………………………………………………….23
Question 1
1.1 Print Chart

1.2Flowchart
 START

Input

Processing

Output

STOP
1.3 Pseundocode

1. - Problem Statement
- A candy company wants a list of its best-selling items, including the item number
and the name of candy. Best-selling items are those that sell over R2, 000 per month.
Input records contain fields for the item number (three digits), the name of the
candy (20 characters), the price per Rands (four digits, two assumed decimal places),
and the quantity in Rands sold last month (four digits, no decimals).

2. Understand the problem

-A candy shop wants a list of its best-selling items, including the item number and
the name of candy. Best selling items are those that are over R2,000 per month. The
company want to input records of items number of (three digits), the name of the
candy (20 characters), the price per rands (four digits, two assumed decimal places),
and the quantity in Rands sold last month (four digits, no decimals).

3. Simplify the Problem

-The company want record of their items of number of 3 digits and the name of
candy, price per rands and the quantity of rands sold last month.

4. Plan how to write a Pseundocode.

1. Start the programme
2. Enter/ input the records of items number of(three digits),and the name of
candy(20 character)
3. Print the Output
4. End the Program
 5. Pseundocode

START THE PROGRAMME,

Enter/ Input Item number (three digits)

Enter/input the name of candy (20 characters)

Enter/input price per rands (four digits, two assumed decimal

place)

Enter quantity in rands sold last month (four digits)

If candyQuantity > 2000 then print candynum,

name

End the Programme.

Start,

Preform Items and name ()

While not eof

preform main loop ()

endwhile

perform finishup ()

Stop

Items and names ()

Declaring variable

Open files

preform headings ()
read candyRec

return

headings ()

printheading1

printheading2

return

mainLoop ()

if candyQuantity > 2000 then

print candyNum, candyName

end if

read candyRec

return

finishUp ()

close files

return
Question 2
2.1.1 Hierarchical Diagram

Sales

Fields

Item Price Item type

Numeric Character

Two Decimal 20 Character

 2.1.2 Pseudocode

1. Problem Statement
-A shop owner needs a weekly sales report. The output consists of a printed report
titled Item Sales, with column headings type of item and price. Fields printed on
output are: type of item and price. After all records print, a footer line end of report
prints. The input file description is shown below.

2. Understand the problem

-A shop owner needs a weekly sales report. The output consists of a printed report
titled Item Sales, with column headings type of item and price.

3. Simplify the Problem

-The shop owner needs a weekly sales report. The output must consists of a printed
report titled item Sales, with column headings type of item and price.

4. Plan how to write Pseundocode.

 Start the programme
 Enter/ input the weekly sales report and the output consist of a printed
report.
 Print the Output
 End the Program

5. Pseudocode

START THE PROGRAMME,

Enter/input title Name

Enter/input Column headings named type of item and type of price

Enter/input item type

 Enter/input item price

Print the output

END THE PROGRAMME.

Start

perform headings ( )

While not eof

Perform main Loop ( )

end while

perform finish Up ( )

Stop

Item type and Prices ( )

declare variables

Item Rec

Char Item Type

num Item Price

char head1 = "Item TYPE"

char head2 = "Item PRICE"

footer = "END OF REPORT"

open files TYPE OF ITEM AND TYPE OF PRICE, Printer

 perform headings ( )

read ItemsRec

return

mainLoop ( )

Print ITEM Type, item Price

read Rec

return

Finish Up ( )

Print footer

close files Item, Printer

return

headings( )

print head1

print head2

return
 2.2 Pseudocode


Start,
Print even numbers ()

Even Number= 0

Even Number= Even number + 1

While even number != -1

If even number=2*N

Then print even number

End while

return

 Start

perform headings ( )

While not eof

Perform main Loop ( )

end while

perform finish Up ( )

Stop

Numb N and print even numbers ( )

declare variables

number Rec

Char N
 number N

char head1 = "N"

numeric head2 = "-even number"

footer = "END OF REPORT"

open files , Printer

perform headings ( )

read numerNRec

return

mainLoop ( )

Even number

read Rec

return

Finish Up ( )

Print footer

close , Printer

return

headings( )

print head1

print head2
if even number=2*N

Print Even number

End while

Return

Question 3
3.1.1 Rules for Creating or naming Variable.

 You must use a letter as the first Character.

 You can`t use a space, period (.), exclamation mark (!), or the character @,&,
$, # in the name.
 Name can`t exceed 255 character in length.
 Generally, you shouldn’t use any names that are the same as the functions,
statements, and methods in Visual Basic. You end up shadowing the same
keywords in the language. To use an intrinsic language function, statement,
or method that conflicts with an assigned name , you must explicitly identify
it. Precede the intrinsic function, statement, or method name with the name
of the associated type library. For example, if you have a variable called Left
you can only invoke the Left function using VBA Left.
 You can`t repeat names within the same level of scope. For example, you
can`t declare two variable named age within the same procedure. However,
you can declare a private variable named age and a procedure-level variable
named age within the same module.

3.1.2 Variables used for coding the Application.

 Length (cm) - For inputting length (Length is always given or calculated)
 Height(cm) -For the purpose of inputting Height( Height is always given or
calculated)
 Area(cm)^2 -For inputting Area (Area=Length * Breath)
3.1.3 Flowchart

START

Input

Processing

Decision

Output

STOP
3.1.4 Hierarchical Diagram

LCD MONITOR SIZE

Area

Formular Calculations

Assigning Values Total area

 3.2

 Project Management- Project Management complements the SDLC when it

comes to Project Quality. It provides a method of managing these unique
project efforts, which increases the odds of attaining cost, schedule and
quality goals. Since not all projects warrant the same level of cost, schedule
and quality goals, it is important to define, as part of the project
management process what these objectives are. Is the customer constraining
the time of the project, do they have a limited budget, or are they looking for
a "cheap" vs. "high-performance" application? These questions are critical in
ensuring that the SDLC efforts are not under- or over-designing the
application, which will lead to a dissatisfied customer.
The primary benefits of a good Project Management Process will:
Provide consistency of success with regard to Time, Cost, and Quality
objectives Ensure customer expectations are met Collect historical
information/data for future use Provide a method of thought for ensuring all
requirements are addressed through a comprehensive work definition
process Reduce Risks associated with the project Minimize scope creep by
providing a process for managing changes.

 Feasibility Assessment-This is the first phase in the systems development

process. It identifies whether or not there is the need for a new system to
achieve a business’s strategic objectives. This is a preliminary plan (or a
feasibility study) for a company’s business initiative to acquire the resources
to build on an infrastructure to modify or improve a service. The company
might be trying to meet or exceed expectations for their employees,
customers and stakeholders too. The purpose of this step is to find out the
scope of the problem and determine solutions. Resources, costs, time,
benefits and other items should be considered at this stage.
 Feasibility is defined as the practical extent to which a project can be
performed successfully. To evaluate feasibility, a feasibility study is
performed, which determines whether the solution considered to accomplish
the requirements is practical and workable in the software. Information such
as resource availability, cost estimation for software development, benefits
of the software to the organization after it is developed and cost to be
incurred on its maintenance are considered during the feasibility study. The
objective of the feasibility study is to establish the reasons for developing the
software that is acceptable to users, adaptable to change and conformable to
established standards. Various other objectives of feasibility study are listed
below.

 Data and Information Gathering Techniques-Gathering requirements for the

project is the most important part of the SDLC for project managers and
internal stakeholders of a project. During this phase, the customer states the
expectations of the project including who will use the product, how the
customer will use the product, and the specific information included with any
special customer requirements related to the software. The customer meets
with business managers and analysts to provide the requirements. It is
important for the project team to understand the needs of the customer
because this information is critical to developing the product the customer
requests.

 After the customer provides requirements for the product, the project
manager and members of the project team begin to analyse the
requirements. The business managers analyse each requirement to ensure
the requirement can be included in the software without causing breaks or
problems with system functionality.
 For example, Lane wants to develop a software application that will help
users find inventory in retail stores faster. Lane provides the following
customer requirements to his project manager:

 The software must include all inventory in each retail store Each retail store
has the same inventory part numbers There are five stores in three states The
application must be able to provide accurate inventory availability within 60
seconds of performing the search

 Documentation-For a programmer reliable documentation is always a must.

The presence of documentation helps keep track of all aspects of an
application and it improves on the quality of a software product. Its main
focuses are development, maintenance and knowledge transfer to other
developers. Successful documentation will make information easily
accessible, provide a limited number of user entry points, help new users
learn quickly, simplify the product and help cut support costs. Documentation
is usually focused on the following components that make up an application:
server environments, business rules, databases/files, troubleshooting,
application installation and code deployment.

 Server Environments

 Detailed documentation about an application and its environments is always

a must. This information will help with setting up new environments for your
application and it should present the location and function of the systems
that run your services. Things that should be specified here are
the application name/version, server name, IP, code directory, URL to the
application, operating system, user account information and a point of
contact.

 Business Rules

 Business rules documentation help new additions to the team adapt faster to
the working habits of the company. It provides information on how the
product works and why. Business rules documentation can easily be
supported with requirements documents if available. This will speed up a
developer's learning curve significantly. In addition to business rules, a help
document, FAQs, or user guide can help highlight the main points of an
application for a developer who needs context for the application they are
supporting.

 Database/Files

 Database information is mandatory for porting, reverting, sharding,

migrating and so on. It is important to know the type of database, the server
information, the version but most importantly to have a data model diagram.
Documentation of the database will make bringing additions to the table,
modifications to the structure and types, additions of indexes and keys much
more simpler and easier to control/debug. Also, if an application presents a
file transfer functionality, it is recommended to document which way the
transfer is made, through which protocol and data types, if and what SSL
certificates are needed.

 Troubleshooting

 The troubleshooting documentation helps when running into production

issues. Most technical issues should have error codes that should help with
troubleshooting. In this document there should also be included an FAQ
 section to deal with general or usual problems (such as configuration issues).
The errors should be documented split by type of error, module where it
comes from, and level of error (exception, warning, critical, etc...).

 Application Installation

 Installation and configuration documents are useful for when developers

need to set up new or additional application environments. If possible, the
steps should be detailed and easy to follow and can include screenshots if
necessary. Anyone should be able to follow the steps and successfully install
an application. Having the steps identified will help the installer prevent
problems because of missing parts of an application. Details such as
necessary software, libraries, and application server versions, can be included
to ensure the environment will be compatible and set up as intended.

Code

 The code documentation is the backbone of every application. Code

documentation can be split in multiple parts. The first one, the most helpful
for programmers are the comment blocks. These will be found through every
file explaining classes, methods, parameters, possible errors. Then comes
the specific file documentations. These are usually generated through a third
party script which will parse a file and, based on the comment blocks, will
create an explicit PDF. Afterwards there should be information regarding
the code repository, where the file updates are found, and where they need
to be moved. In addition, there should be step-by-step instructions on how to
create an application package or a build to be deployed.
References:

1. David j, Anderson. 1990. Lean Software Development. Chapter 5

P127,128,129
2. Florian, M.1999. Efficiency in Development Workflows. Chapter 4 P227
3. Jason, G.2000.Hyper- Free Principles For Software Developers. Chapter 6
P32,33
4. Joyce, F. 1992. Programming Logic and Design Comprehensive. Chapter3
P166
5. Joyce, F. 2007. Programming Logic and Design Comprehensive.6th edition.
Chapter 7. P254
6. Jonathan, B.2007. Programming From The Ground Up. Chapter 2 P22
7. Karl, S.2005. Foundations Of Programming.Chapter2 P24