Design Programing Logic Final Exam
Design Programing Logic Final Exam
1. __________provide a simplified picture of the 7. Which one is not true about the
relationships between the program activities and programming phases?
the desired outcomes of the program A. Understand the problem
A. Logic models B. Plan the logic
B. Program planning. C. Selection of diagram
C. Program implementation. D. Code the program
D. None 8. Which one is not the element of
2. Logic model is valuable in supporting all the understanding the problem?
following except one. A. May be the most difficult phase
A. Program planning. B. Users may not be able to articulate
B. Program implementation. their needs well
C. Program monitoring. C. User needs may be changing
D. Program execution. frequently
3. It defines a picture of why and how you believe a D. None
program or a policy will work. 9. Testing the program is
A. Program planning. _______________
B. Program implementation. A. Execute it with sample data and
C. Program logic check results
D. Program monitoring. B. Identify logic errors and correct
4. We use a logic model for all the following them
activities except one. C. Choose test data carefully to
A. Brings detail to broad goals. exercise all branches of the logic
B. Helps identify gaps in program logic and D. All
clarify assumptions. 10. Which one is a document used in a
C. Builds understanding and promotes consensus. design or procurement process?
A. Program planning
D. Makes implicit underlying beliefs.
B. Setting framework
5. One of the following will be the starting point in
C. Program of requirements
many cases you should do before doing any of the
D. Monitoring planning
actual work of program.
11. software development method is
A. Design Document
called____________
B. Coding program
A. Preliminary investigation
C. Testing program
B. Programming design
6. The aim of a program of requirements is
_____ C. Software life cycle
A. To lay down a clear framework for everyone D. Maintenance of program
involved in the project. 12. In which of the following you defining
B. To set the criteria for everyone involved in the the problem and Suggesting a solution?
project. A. Preliminary investigation
C. To inform the criteria for everyone involved in the B. Design phase
project.
C. Implementation phase
D. All
D. Testing phase
1
Debre Markos Poly Technic Collage
Final Exam For Designing Program Logic
Full Name______________________ID__________Sec_____
13. Which one is not a primary activities 16. The way data are organized in a
involved in the analysis phase are as computer’s memory is said to
follows: be_______?
A. Gathering business requirement A. Algorithm
B. Creating process diagrams B. Data Structure
C. Performing a detailed analysis C. Pseudo code
D. Documentation of the project D. Data gathering technique
14. In which phase we describe the desired 17. ____is used in planning an algorithm with
sketching out the structure of the program before
features and operations of the system
the actual coding takes place.
including business rules, pseudo-code, A. Narrative
screen layouts, and other necessary B. Flowchart
documentation? C. Algorithm
A. Preliminary investigation D. Pseudo-code
B. Design phase 18. Which tools is used to analyze a problem and
C. Implementation phase visualize a solution using the top down design
approach?
D. Testing phase
A. RAD
15. The sequence of computational steps to B. HIPO chart
solve a problem is said to be
_________? C. DFD
25. It defines the relationship between the entities in terms of numbers E. Solve problem
2
Debre Markos Poly Technic Collage
Final Exam For Designing Program Logic
Full Name______________________ID__________Sec_____
Answer sheet
M.C 1__2__3__4__5__6__7__8__9__10__11__12__13__14__15__16__17__18__19__20__
C.M 21__22__23__24__25__26__
3
Debre Markos Poly Technic Collage
Final Exam For Designing Program Logic
Full Name______________________ID__________Sec_____
________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
4
Debre Markos Poly Technic Collage
Final Exam For Designing Program Logic
Full Name______________________ID__________Sec_____
41. Software _________________ and _________________ are difficult because a developer cannot
test forever, and it is hard to know how much evidence is enough.
42. Why we need gaining feedback in program development?
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
43. In gaining feedback you should focuses on ;
______________________________________________________________________________
______________________________________________________________________________
Answer Key
1. A 2. D 3. C 4. D 5. A
6. A 7. C 8. D 9. D 10. C
11. C 12. A 13. D 14.B 15. A 16. B 17.D 18.B 19.B 20.C
21. E 22. B 23.D 24.C 25.A 26.F
27. Draw the flow chart that calculates grade for ten students based on the scale: >80-A, >60-B, > 50-C,
>40-D, <40-F.
5
Debre Markos Poly Technic Collage
Final Exam For Designing Program Logic
Full Name______________________ID__________Sec_____
28. Write a pseudo-code that calculates grade hint mark >=80 grade A, mark >=60 grade B, mark
>=50 grade C, mark >=40 grade D, F<40.
ACCEPT Mark, Name
IF Mark>80 Then
Grade A
ELSE IF Mark >60 Then
Grade B
ELSE IF Mark >50 Then
Grade C
ELSE IF Mark >40 Then
Grade D
ELSE
Grade F
ENDIF
Display Grade, Name
6
Debre Markos Poly Technic Collage
Final Exam For Designing Program Logic
Full Name______________________ID__________Sec_____
Project planning standards may obviously vary from project to project, but the goals are
usually the same to complete the project within the time-frame and without exceeding the
allotted resources.
30. Project planning standards should include
Quality Assurance Necessities Testing Techniques
Risk Management Plan Documentation and Portfolio
Security Measures Requirements
31. Why we need program structure diagram?
Program structure diagram is used for showing the breakdown of some particular system to its
lowest manageable levels. Such levels may be used in a structured programming for arranging
the program modules into a “tree”.
32. List the type of software you can use to draw structural diagram
Data Flow Diagrams, IDEFO Diagrams,
Entity-Relationship Diagram (ERD), Rapid UML.
Graphic User Interface,
33. List the kinds of relationships in UML
Dependencies Associations
Generalizations Realization
34. List scope document elements you should define in project. (6 point)
A well defined scope document can save you from major headaches by defining the following
project elements:
Project goals Key milestones
Requirements Assumptions
Major deliverables Constraints
35. The list of possible elements you should consider adding to your scope statement.
The list of possible elements you should consider adding to your project scope statement are
Business case and goals Assumptions
Project description and deliverables Exclusions
Acceptance criteria Costs
Limitations Agreement
36. What a scope of work document?
A scope of work (SOW) document is an agreement on the work you're going to perform on the project.
The document includes it's a section of the document that delineates the major phases across the schedule
of the project's duration.
37. The three layers of master data service implementations are characterized with
Core services,
Object services,
7
Debre Markos Poly Technic Collage
Final Exam For Designing Program Logic
Full Name______________________ID__________Sec_____
Business application services,
38. The most basic reference table is just a typical table in third or second normal form.
39. In practice, software validation activities may occur both during, as well as at the end of the
software development life cycle to ensure that all requirements have been fulfilled.
40. Software verification looks for consistency, completeness, and correctness of the software and
its supporting documentation.
41. Software verification and validation are difficult because a developer cannot test forever, and it
is hard to know how much evidence is enough.
42. Feedback helps you learn. Feedback makes you and your work better. Whether you follow
specific Agile practices or not, feedback early and often is a critical component of being more
successful.
43. In gaining feedback focused on optimizing the following kinds of feedback workflows:
Feedback on Priorities
Feedback on Design
Feedback on Working Software:
Feedback on Code