CAD630 Systems Analysis, Design and Development
Examination Date - SUN 10JAN2010
Examination Time - FROM 9.00AM-12.00NN
Exam Requirements
Chap 1 – the systems development environment - read theory
Chap 2 – identifying and selecting systems development project : prototyping, others read at a glance)
Chap 3 - initiating and planning systems development project
Chap 4 – determining system requirements (read theory, focus on - JAD, others read at a glance)
Chap 5 – structuring system process requirements - focus on construction/designing of DFD, understand theory to create the diagram
Chap 6 – structuring system logical requirements (read theory - decision tree, structured English)
Chap 7 – structuring system data requirements - focus on construction/designing of ER Diagram, understand theory to create the diagram
Chap 8 – designing databases - focus on creating databases (consist of many tables and perform normalization), understand theory to create the diagram
Chap 9 – designing forms and reports - read theory
Chap 10 – designing interfaces and dialogues - focus on creating user interface, do not emphasize on theory
note: all topics should be read to ensure overall understanding, focus on certain topics, may help you to practice on the hands-on/diagram task
For diagram in part B, only one question would be asked either DFD/ERD, but you need to know/study both.
All the best for the exam
EXAMINATION FORMAT
No objective questions, consist of short answers / essay / diagramming / theoretical
• Part A: 5 Q, answer 4 only (Test on theory - understanding/knowledge/comprehension of subject)
• Part B: 2 or 3 Q, answer 2 only (Test on diagramming/drawing/designing - application/analysis/synthesis type of question)
Showing posts with label 0909 Semester. Show all posts
Showing posts with label 0909 Semester. Show all posts
Wednesday, December 30, 2009
CNM640 Examination Requirements
CNM640 Network Management
Date of Examination - SAT 9JAN2010
Time of Examination - FROM 2.30PM-5.30PM
EXAM REQUIREMENTS
Chapter One,
- Study on Analyzing Business Goal - all
Chapter Two
- Study on Analyzing Technical Goal - focus on Availability and Scalability
Chapter Three
- Focus on Wi-fi Characterizing and Constraint
Chapter Four
- No need...
Chapter Five
- Study on Designing a Network Topology - focus on Hierarchical
Chapter Six
- No need to study.. OK.
Chapter 14
- Study all.
Hopefully all of you can answer all the questions, but before u focus on certain chapter... please read all the chapter above, coz there are multiple set of question.
- Study on Analyzing Business Goal - all
Chapter Two
- Study on Analyzing Technical Goal - focus on Availability and Scalability
Chapter Three
- Focus on Wi-fi Characterizing and Constraint
Chapter Four
- No need...
Chapter Five
- Study on Designing a Network Topology - focus on Hierarchical
Chapter Six
- No need to study.. OK.
Chapter 14
- Study all.
Hopefully all of you can answer all the questions, but before u focus on certain chapter... please read all the chapter above, coz there are multiple set of question.
Saturday, December 26, 2009
CNM640 Network Management Assignment 2 Q
The question still based on your current office and today situation. (Please read Chapter 5 till Chapter 6)
Briefly explain on your network topology that been used at your office:-
- Draw the topology using Visio or DIA
- Why the management or you as a Network Manager choose that topology
- List all the disadvantages of your topology
- What is the Addressing Scheme and Naming that you are using at your office and Why?
- Summary.
- Draw the topology using Visio or DIA
- Why the management or you as a Network Manager choose that topology
- List all the disadvantages of your topology
- What is the Addressing Scheme and Naming that you are using at your office and Why?
- Summary.
(20 Marks)
Requirements:
- Front Page
- Table of Content
- All the documentations above not more than 12 pages.
- Font Size 12 | 1.5 - 1.5 Spacing | Arial or Times New Roman ONLY
How to answer?
- The marks will be on how you elaborate of all the scenarios. You can refer to Chapter 1 until Chapter 3.
- You can do the citation from other materials to support all of your answers.
- Extra marks will be given if you can provide supporting information to the solution for each problem that occurs at your places.
- You can contact me (xxx-xxx xxxx / hidzuan@gmail.com) if there are any enquiries regarding this assignment.
- The submission is through email stating your name and your matric number.
CPM650 ICT Project Management Assignment 3 Q
CPM650 ICT PROJECT MANAGEMENT
Assignment 3 Dec 2009
1. The process of authorizing a new or continuing an existing project.
2. An ongoing process that defines the mission, objectives, and strategies of an organization.
3. A statement that makes it clear what business a company is in.
4. A series of statements that express an organization's qualitative and quantitative goals for reaching a desired future position.
5. The method by which an organization attempts to achieve its mission and objectives.
6. An orderly means of assessing the information needs of an organization and defining the systems, databases, and technologies that will best satisfy those needs.
7. A form used in most organizations to request new development, to report problems, or to request new features within an existing system.
8. A generic information systems planning methodology that attempts to gain a broad understanding of the information system needs of the entire organization.
9. A generic information systems planning methodology that identifies and defines information systems development projects based upon solving operational business problems or taking advantage of some business opportunities.
10. The justification that presents the economic, technical, operational, schedule, legal and contractual, and political factors influencing a proposed information systems project.
11. A comparison of the financial benefits and costs associated with a development project.
12. A benefit that can be measured in dollars and with certainty.
13. A benefit that cannot be easily measured in dollars or with certainty.
14. A cost that can be measured in dollars and with certainty.
15. A cost that cannot be easily measured in terms of dollars or with certainty.
16. A cost associated with project start-up and development or system start-up.
17. A cost resulting from the ongoing evolution and use of a system.
18. The use of a variety of analysis techniques for determining the financial feasibility of a project.
19. The rate of return used to compute the present value of future cash flows.
20. The current value of a future cash flow.
21. A type of cost-benefit analysis to identify when (if ever) benefits equal costs.
22. An assessment of the development organization's ability to construct a proposed system.
23. The degree to which a proposed system solves business problems or takes advantage of business opportunities.
24. The degree to which the potential time frame and completion dates for all major activities within a project meet organizational deadlines and constraints for affecting change.
25. An evaluation of how key stakeholders within the organization view the proposed system.
26. The process of analyzing an organization's activities to determine where value is added to products and/or services and the costs incurred for doing so.
27. A project selection method that uses a weighted scoring method for a variety of criteria to contrast alternative projects or system features.
28. A short document prepared for the customer during project initiation that describes what the project will deliver and outlines generally at a high level all work required to complete the project.
29. The process of progressively elaborating and documenting the project work plan in order to effectively manage a project.
30. An online or hard-copy repository for all project correspondence, inputs, outputs, deliverables, procedures, and standards established by the project team.
31. A document prepared for the customer that describes what the project will deliver and outlines generally at a high level all work required to complete the project.
32. A major outcome and deliverable from the project scope definition process that contains the best estimate of a project's scope, benefits, costs, risks, and resource requirements.
33. The process of subdividing the major project deliverables – as identified in the project scope statement – into smaller, more manageable activities in order to make more accurate cost, task duration, and resource estimates.
34. The process of obtaining formal acceptance from the project stakeholders of a project’s scope.
35. A formal process for assuring that only agreed-upon changes are made to the project’s scope
36. A progressive, uncontrolled increase in project scope.
37. The process of defining project activities, determining their sequence, and estimating their duration.
38. The reiteration of the processes of activity definition, sequencing, and duration estimation as part of schedule development.
39. The process of subdividing tasks to make them more easily manageable.
40. The output from the process of dividing a product into its individual components.
41. The output that results from the process of dividing the entire project into manageable tasks (usually presented as a hierarchical chart or in tabular form).
42. A document that accompanies the WBS and provides additional information about the individual components of the WBS.
43. A document containing the WBS and the WBS dictionary; which specifies the deliverables and components of a project and serves to measure any deviations from that baseline during project execution.
44. The time required by one task before another task can begin.
45. The process of identifying and defining activities that must be performed to produce project deliverables.
46. Small components used to plan, schedule, execute, monitor, and control the project.
47. The process of developing a network diagram and updating the activity list from the activity definition phase.
48. A schematic display that illustrates the various tasks in a project as well as the sequential relationship among those tasks.
49. The time delay between the completion of one task and the start of the successor.
50. A network diagramming technique that uses boxes and rectangles connected by arrows to represent activities and their precedence relationships.
51. A network diagram consisting of arrows to represent activities and their precedence relationships, and nodes to represent project milestones.
52. A template developed from previous projects used to shorten the development time of network diagrams.
53. The relationship of activities that cannot be performed in parallel.
54. The relationship of activities based on the preferences of project managers; often based on best-practices procedures.
55. The relationship of project activities and external events such as the delivery of project components.
56. Important dates with a project schedule that are meaningful in terms of the completion of specific sets of project events.
57. A bar chart that employs timelines and other types of symbols to illustrate the project schedule, where activity names are listed on the vertical, and durations on the horizontal axis.
58. An activity of zero duration that is used to show a logical relationship or dependency in a network diagram.
59. __________ is a method of scheduling that considers limited resources when creating a project schedule and includes buffers to protect the project completion date.
60. Which of the following is not a best practice that can help in avoiding scope problems on IT projects?
Assignment 3 Dec 2009
1. The process of authorizing a new or continuing an existing project.
2. An ongoing process that defines the mission, objectives, and strategies of an organization.
3. A statement that makes it clear what business a company is in.
4. A series of statements that express an organization's qualitative and quantitative goals for reaching a desired future position.
5. The method by which an organization attempts to achieve its mission and objectives.
6. An orderly means of assessing the information needs of an organization and defining the systems, databases, and technologies that will best satisfy those needs.
7. A form used in most organizations to request new development, to report problems, or to request new features within an existing system.
8. A generic information systems planning methodology that attempts to gain a broad understanding of the information system needs of the entire organization.
9. A generic information systems planning methodology that identifies and defines information systems development projects based upon solving operational business problems or taking advantage of some business opportunities.
10. The justification that presents the economic, technical, operational, schedule, legal and contractual, and political factors influencing a proposed information systems project.
11. A comparison of the financial benefits and costs associated with a development project.
12. A benefit that can be measured in dollars and with certainty.
13. A benefit that cannot be easily measured in dollars or with certainty.
14. A cost that can be measured in dollars and with certainty.
15. A cost that cannot be easily measured in terms of dollars or with certainty.
16. A cost associated with project start-up and development or system start-up.
17. A cost resulting from the ongoing evolution and use of a system.
18. The use of a variety of analysis techniques for determining the financial feasibility of a project.
19. The rate of return used to compute the present value of future cash flows.
20. The current value of a future cash flow.
21. A type of cost-benefit analysis to identify when (if ever) benefits equal costs.
22. An assessment of the development organization's ability to construct a proposed system.
23. The degree to which a proposed system solves business problems or takes advantage of business opportunities.
24. The degree to which the potential time frame and completion dates for all major activities within a project meet organizational deadlines and constraints for affecting change.
25. An evaluation of how key stakeholders within the organization view the proposed system.
26. The process of analyzing an organization's activities to determine where value is added to products and/or services and the costs incurred for doing so.
27. A project selection method that uses a weighted scoring method for a variety of criteria to contrast alternative projects or system features.
28. A short document prepared for the customer during project initiation that describes what the project will deliver and outlines generally at a high level all work required to complete the project.
29. The process of progressively elaborating and documenting the project work plan in order to effectively manage a project.
30. An online or hard-copy repository for all project correspondence, inputs, outputs, deliverables, procedures, and standards established by the project team.
31. A document prepared for the customer that describes what the project will deliver and outlines generally at a high level all work required to complete the project.
32. A major outcome and deliverable from the project scope definition process that contains the best estimate of a project's scope, benefits, costs, risks, and resource requirements.
33. The process of subdividing the major project deliverables – as identified in the project scope statement – into smaller, more manageable activities in order to make more accurate cost, task duration, and resource estimates.
34. The process of obtaining formal acceptance from the project stakeholders of a project’s scope.
35. A formal process for assuring that only agreed-upon changes are made to the project’s scope
36. A progressive, uncontrolled increase in project scope.
37. The process of defining project activities, determining their sequence, and estimating their duration.
38. The reiteration of the processes of activity definition, sequencing, and duration estimation as part of schedule development.
39. The process of subdividing tasks to make them more easily manageable.
40. The output from the process of dividing a product into its individual components.
41. The output that results from the process of dividing the entire project into manageable tasks (usually presented as a hierarchical chart or in tabular form).
42. A document that accompanies the WBS and provides additional information about the individual components of the WBS.
43. A document containing the WBS and the WBS dictionary; which specifies the deliverables and components of a project and serves to measure any deviations from that baseline during project execution.
44. The time required by one task before another task can begin.
45. The process of identifying and defining activities that must be performed to produce project deliverables.
46. Small components used to plan, schedule, execute, monitor, and control the project.
47. The process of developing a network diagram and updating the activity list from the activity definition phase.
48. A schematic display that illustrates the various tasks in a project as well as the sequential relationship among those tasks.
49. The time delay between the completion of one task and the start of the successor.
50. A network diagramming technique that uses boxes and rectangles connected by arrows to represent activities and their precedence relationships.
51. A network diagram consisting of arrows to represent activities and their precedence relationships, and nodes to represent project milestones.
52. A template developed from previous projects used to shorten the development time of network diagrams.
53. The relationship of activities that cannot be performed in parallel.
54. The relationship of activities based on the preferences of project managers; often based on best-practices procedures.
55. The relationship of project activities and external events such as the delivery of project components.
56. Important dates with a project schedule that are meaningful in terms of the completion of specific sets of project events.
57. A bar chart that employs timelines and other types of symbols to illustrate the project schedule, where activity names are listed on the vertical, and durations on the horizontal axis.
58. An activity of zero duration that is used to show a logical relationship or dependency in a network diagram.
59. __________ is a method of scheduling that considers limited resources when creating a project schedule and includes buffers to protect the project completion date.
60. Which of the following is not a best practice that can help in avoiding scope problems on IT projects?
CPM650 ICT Project Management Assignment 2 Q
Dear students,
Read the running case provided at the end of Chapters 7, 8, 9 and 10 of the text book and complete the tasks given at the end of each chapter. The pages are listed below.
Chapter 7 pg 296 Exercises: no. 1
Chapter 8 pg 346 Exercises: no. 2
Chapter 9 pg 399 Question: no. 3
Chapter 10 pg 440 Question: no. 3
You may submit the assignment in soft copy or hardcopy form.
Due date is 20th December 2009.
Read the running case provided at the end of Chapters 7, 8, 9 and 10 of the text book and complete the tasks given at the end of each chapter. The pages are listed below.
Chapter 7 pg 296 Exercises: no. 1
Chapter 8 pg 346 Exercises: no. 2
Chapter 9 pg 399 Question: no. 3
Chapter 10 pg 440 Question: no. 3
You may submit the assignment in soft copy or hardcopy form.
Due date is 20th December 2009.
CPM650 ICT Project Management Assignment 1 Q
Read the running case provided at the end of chapter 4, 5 and 6 of the text book and complete the tasks given at the end of each chapter. The pages are listed below.
You may submit the assignment in soft copy or hard copy.
Chapter 4 pg 174-177
Chapter 5 pg 213-214
Chapter 6 pg 258-259
CAD630 SADD Assignment 3 Q
Choose either ONE (1) of the following titles.
a) Clinic Management System
b) Hotel Registration System
Question 1
Consider the design of any ONE (1) of the above system.
a) Clinic Management System
b) Hotel Registration System
Question 1
Consider the design of any ONE (1) of the above system.
- Draw an Entity-Relationship (E-R) Diagram for the system.
- Describe the relevant users, tasks, and displays involved when designing the interface for such a system.
- Design the user interface which shows possible screen designs for the system.
Deadline before 25Dec, 2009.
CAD 630 SADD Assignment 2 Q
Consider a system for a clinic management system. It is a complete workflow of medical clinic’s operation which involve the stakeholders such as the doctors, patient, clinic staffs, …etc
Among basic functions of the system are:
· Register patients
· Manage patient visit records
· Appointment and scheduling
· Consultation & physical exams
· Manage cash collection/medical billing
· Manage pharmacy and prescriptions/dispensary
· Manage drugs and inventory/inventory control
· Supplier management:
o Billing to panels
o Tracking of payments due and received from panels
o Tracking of payments due and received from panels/drug suppliers
· View of transaction and management reports
· Manage patient queue
Draw the context diagram and data flow diagram for the system.
CNM640 Network Management Assignment 3 Q
Based on Assignments 1 and 2, we need a concrete documentation on our new network design from the existing. So the task will be "Documenting Your Network Design" based on Chapter 14. The content in your document should include:
- Executive Summary
- Project Goal
- Project Scope
- Design Requirement
- Implementation Plan
- Project Budget
Assuming this documentation will be submitted to top management, there is no need for technical details.
Tuesday, October 27, 2009
CAD630 SADD Assignment 1 Q
Question 1.
Suppose you were an analyst developing a new information system to automate the sales transactions and manage inventory for each retail store in large chain. Every store will be installed with the system and the system will exchange data with a mainframe computer at the company's head office. Discuss what type of methodology would you use? Describe the reasons why.
Your answer should be typed at the minimum of 2 pages long.
Suppose you were an analyst developing a new information system to automate the sales transactions and manage inventory for each retail store in large chain. Every store will be installed with the system and the system will exchange data with a mainframe computer at the company's head office. Discuss what type of methodology would you use? Describe the reasons why.
Your answer should be typed at the minimum of 2 pages long.
Question 2.
Suppose you are a project manager using a waterfall development-based methodology on a large and complex project. Your manager just read the latest article in ComputerWorld magazine that advocates replacing this methodology with prototyping and comes to your office requesting you to switch. What do you say? Give thorough justification to your manager regarding this issue. Type your answer in a written form discussing this issue.
Your answer should be typed at the minimum of 2 pages long.
Overall total marks = 20%
CNM640 Network Management Assignment 1 Q
You are in-charge of the Network Management of your company. Due to the business opportunities, your top-level management required you as a Network Manager to do a research on the existing network problems before moving to a new building. You have to prepare all the documentations below before presenting to the stake holders:
- Introduction of your company/department
- Network diagram at your company
- Problem with the current network problem
- Solution from you as a Network Manager to cater all the problems above
- Advantages and Disadvantages
- Summary
Requirements:
- Front Page
- Table of Content
- All the documentations above not more than 12 pages.
- Font Size 12 | 1.5 - 1.5 Spacing | Arial or Times New Roman ONLY
How to answer?
- The marks will be on how you elaborate of all the scenarios. You can refer to Chapter 1 until Chapter 3.
- You can do the citation from other materials to support all of your answers.
- Extra marks will be given if you can provide supporting information to the solution for each problem that occurs at your places.
- You can contact me (xxx-xxxxxxx / hidzuan@gmail.com) if there are any enquiries regarding this assignment.
Subscribe to:
Posts (Atom)