De La Salle University-Manila  College of Computer Studies

Course Syllabus

SYSIMTE / Systems Design, Implementation and Testing

Term : Term 1, AY 2011-2012

Credit Units : 3.0
Faculty : Ms. Christine Mae Tavera ([email protected])
E-Group : [email protected]

I. Course Description:

This course introduces the concept of dealing with software as an engineering product that requires
analysis, design, implementation, testing, and maintenance. It focuses on the concepts and principles
of software requirements engineering, its tools, techniques and methods for modeling software
systems.

II. Course Objectives:

This course aims to study the software engineering concepts, particularly in the analysis phase and the
design phase, and to apply the various principles and techniques in software engineering. At the end of
the course, the students should be able to:

1. know the tools and techniques used in planning, analysis, and design;
2. know the different methodologies for software development;
3. produce an analysis and design document applying the different principles and techniques in
software engineering;
4. employ critical/analytical thinking, good reasoning, and good decision making in the
development of a project;
5. acquire technical writing and layout skills by writing a project documentation;
6. acquire good oral communication skills and presentation skills through a project defense; and
7. gain leadership and management skills by working in a team.

III. Course Outline:

Topic Details Chapter Week Hours

 Discussion of course syllabus and
Course Orientation policies NA 1 3.0
 Formation of the project groups
 Types of Information System
 System Development Methodologies
o Systems Development Life
Introduction to System
Cycle 1 2-3 6.0
Analysis and Design
o Rapid Application Development
o Agile Methodologies
 The Systems Analyst

Page 1 of 5
//cmat
 Topic Details Chapter Week Hours
 Evaluating Systems Request
 Preliminary Investigation
Systems Planning 2 4 1.5
o Problem Analysis
 Evaluating Feasibility
 Interview
 Document Review
Systems Analysis:
 Observation
Requirements 4 4 1.5
 Questionnaires and Surveys
Modeling
 Sampling
 Research
 Data Flow Diagram
Systems Analysis:
 Data Dictionary
Data and Process 5 5-6 6.0
Modeling  Process Description (Reading
Assignment)
 Outsourcing
Systems Analysis:  In-House Software Development
Development  The Software Acquisition Process 7 7 1.5
Strategies  Transition to Systems Design
 Prototyping
Long Quiz 1 NA 7 1.5
 Output Design
Output and User  Printed and Screen Output
8 8 3.0
Interface Design  User Interface Design
 Input Design
 Coding
 Testing the System
 Documentation
Systems  System Installation and Evaluation
10 9 3.0
Implementation  Training
 Conversion
 System Changeover
 Post-Implementation Tasks
 Maintenance Activities
 Managing System Support
Systems Operations,  Managing System Performance
11 10 3.0
Support and Security  Systems Security
 Backup and Recovery
 System Obsolescence
Long Quiz 2 NA 11 1.5
Project Presentation NA 11-13 7.5

IV. Textbook:

Systems Analysis and Design Methods, Philippine Edition (2009)

Gary B. Shelly
Thomas J. Cashman
Harry J. Rosenblatt

Page 2 of 5
//cmat
 V. Other References:

 Bentley, L.D., Whitten, J.L. Systems Analysis and Design for the Global Enterprise, 7th edition.
McGraw-Hill, 2007.
 Kendall, K., Kendall J. Systems Analysis and Design, 7th edition. Prentice Hall, 2008.
 Satzinger, J.W., Jackson, R.B., Burd, S.D. Systems Analysis and Design in a Changing World, 4th
edition. Thomson Learning, 2006.
 Dennis, A., Wixom, B. H., & Roth, R. Systems Analysis and Design , 3rd edition. Hoboken, NJ :
Wiley, 2006.
 ACM sigsoft
 Software Engineering Notes
 dmoz.org/computers/software/software engineering.

VI. Grading System:

Long Quiz 1 - 20%

Long Quiz 2 - 20%
Project Document - 20%
Project Presentation - 20%
Class Participation - 20%
(exercises, seatworks, case analysis, activities and attendance)
TOTAL - 100%
Passing: 70%
VII. Project Details

Students should form a group with 3-4 members each for the project. They have to look for an actual
organization (profit or non-profit) and propose an IT solution based on their needs and problems. The
final output will be a system document and the complete screen design of the system.

Project Outline:

1. Introduction
This section should provide an overview of the project by stating the current trends in Information
and Communications Technology (ICT) globally, locally, and within the industry. (Citations for the
sources used must be provided.) This should also briefly discuss how the company is coping with
the ICT trends, the general problem/s it is experiencing, and how an ICT solution will solve its
problem/s.
2. Review of Related Literature
2.1. Review of Related Concepts
This section should provide a detailed discussion of the concepts that were used as basis for the
framework of the proposed system. Citations for the sources used must be provided.
2.2. Review of Related Systems
This section should provide a detailed discussion of at least five (5) information systems that were
reviewed and used as basis for the framework of the proposed system. This should also provide a
synthesis and a table that will show a comparison of the information systems reviewed in terms of
their strengths and weaknesses. The reader should be referred to the appendix section for the
screenshots and sample forms/reports of the systems reviewed. (Attachment: Screen shots,
sample forms/reports of the systems reviewed)
3. The Existing System
3.1. Company Profile
This section should describe the company in terms of its history, organizational structure, and
nature of business, mission/vision, products/services, suppliers, customers, and competitors. The

Page 3 of 5
//cmat
 reader should be referred to the appendix section for the organizational chart. (Attachment:
Organizational Chart)
3.2. Description of the System (Attachment: DFD of the existing processes of the organization)
This section should detail the inputs and outputs, processes, sources/receivers of data/information,
and data storage locations of the current system. This narrative should be consistent with the data
flow diagram of the existing system. The reader should be referred to the appendix section for the
forms/reports that are used / generated by the system, the data flow diagrams of the existing
system, and the data dictionary of the existing system. (Attachments: Data Flow Diagrams, Data
Dictionary, Existing forms and reports, Interview transcripts)
3.3. Problem Areas
This section should provide a detailed discussion of the main problem/s of the existing system. This
section should also explain the causes of the problem/s.
4. The Proposed System
4.1. System Description
This section should detail the inputs and outputs, processes, sources/receivers of data/information,
data storage locations, and performance and controls of the proposed system. This narrative
should be consistent with the data flow diagram of the proposed system and should highlight the
changes that were made to the existing system. The reader should be referred to the appendix
section for the data flow diagrams and data dictionary of the proposed system. (Attachments: Data
Flow Diagrams, Data Dictionary)
5. Design
5.1. Screen Specifications
This section should provide a narrative that explains the overall screen design. This section should
cite the principles/concepts that were used and how they were applied in designing the screens.
This should also explain the hierarchy/flow of screens. The reader should be referred to the
appendix section for the dialogue tree.
This section should describe each screen using the following format:
Screen Name : <Screen Number in the Dialogue Tree and Screen Name (Example: 0.0 Login
Screen)>
File Name : <Actual file name used>
Description : <Detailed description of the screen, including the functions, controls, and navigations
available>
Layout : <Screen shot>
5.2. Report Specifications
This section should provide a narrative that explains the report design. This section should cite the
basis for designing the reports. The reader should be referred to the appendix section for the actual
reports generated by the proposed system. (Attachment: Sample printouts of the reports of the
proposed system)
This section should describe each report using the following format:
Report Name :
Description :
Prepared By :
Used By :
Volume and Frequency :
Layout :
6. System Testing Plan
This section should describe in detail the specific activities that should be done for each of the four
testing stages.
7. System Implementation
7.1. Resource Requirements
7.1.1. Hardware Requirements
This section should discuss the minimum hardware specifications needed to use the system.
The recommended hardware requirements should also be discussed.
7.1.2. Software Requirements

Page 4 of 5
//cmat
 This section should discuss the minimum software specifications needed to use and maintain
the system.
7.1.3. Human Resource Requirements
This section should discuss who will use and maintain the system. This section should also
provide the skills requirements of the users and maintenance personnel of the system.
7.2. Implementation Plan
7.2.1. Personnel Training
This section should detail the plans for training the users and maintenance personnel of the
proposed system.
7.2.2. System Conversion
This section should discuss the appropriate installation technique for the system. This section
should include a detailed plan for installing or converting to the new system.
7.2.3. Data Conversion
This section should discuss the plans for data conversion.
8. System Maintenance Plan
This chapter should discuss the plans and procedures for maintaining the system based on the four
types of maintenance
9. Conclusion and Recommendations

Appendices
Bibliography
Citations in the documentation should follow the American Psychological Association (APA) format. For
more information on APA Style for electronic references, visit http://www.apastyle.org/elecref.html.
Resource Persons
Personal Vitae

Deadline of the Project: Week 11 (August 9, 2011, classtime. Late submission of documents will
be penalized with a 20% deduction from the presentation grade.)

VIII. Classroom Policies

Please refer to your Student Handbook.

Page 5 of 5
//cmat