Philippine Society of IT Educators Research Committee as of January 30, 2010

Software Development
software customization information systems development for an actual

client (with pilot testing) web applications development (with at least alpha testing on live servers) mobile computing systems *** Infrastructure implications with the introduction of the system should be clearly specified in the final report

Multimedia systems

Network design and implementation; and server farm configuration and management IT Management IS Planning
IT Strategic Plan for sufficiently complex enterprise IT Security Analysis, Planning and Implementation Enterprise Resource Plan Information Systems Strategic Plan

game development e-learning systems interactive systems information kiosks

Analysis and design of a sufficiently complex system

Title Page Executive Summary Table of Contents List of Figures, List of Tables, List of Notations Introduction

Project Context Purpose and Description Objectives Scope and limitations

Review of Related Literature/Systems

Technical Background Methodology

Method of Development Requirements Specification Analysis Design Testing and Evaluation Implementation Plan (If needed)

Results and Discussions Summary, Conclusion and Recommendations

Bibliography Appendices may include the following

Relevant Source Code Evaluation Tool Sample input/output/Reports Users Guide/Manual Curriculum Vitae

Public Presentation is recommended School-based presentation open to the public

Summarizes everything about the project. It includes the idea behind the conceptualization of the project, its significance, the projects major functionalities, the implementation techniques, results, conclusions and recommendations. By reading the Executive Summary the reader will already understand what the whole project is all about. A one to two page Executive Summary is advisable.

This will be the general overview of the project Introduce your project by capturing the readers interest in the first paragraph. Refrain from placing citations or quotes in this section. Avoid beginning with This paper/document/thesis/study/projects, etc. Discuss the problem background and why you decided to develop your project. Whats wrong with the traditional method ?

Provide a short description of the project being specified and its purpose, including relevant benefits (or beneficiaries)
What is your main purpose in doing the project? Who is/are your target clients, end user/s or

beneficiaries of the project? What are the necessary knowledge, programming software, APIs, hardware, etc needed?

Detailed statements or elaboration of the project goal. It states the specific steps on how to achieve the goal of the project.
Studying a particular programming language or

development tool to accomplish the objective is inherent in all projects and need not be included in the objectives.

Describe any global limitations or constraints that have a significant impact on the design of the system/software (and describe the associated impact). Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards

The following are the other possible limitations (the list is not exhaustive):

Hardware or software environment End-user environment Availability or volatility of resources Standards compliance Interoperability requirements Interface/protocol requirements Data repository and distribution requirements Security requirements (or other such regulations) Memory and other capacity limitations Performance requirements Network communications Verification and validation requirements (testing) Other means of addressing quality goals

*Choose Literature or Systems depending on what you will be presenting

Chapter 2 REVIEW OF LITERATURE The Review of Literature showcases previous studies and publications relevant to the project. This chapter gives light as to what motivated the proponent/s in pursuing the specific field of study.

Discuss the theories of the concepts that you are going to apply in System Analysis and Design. Include in-depth discussion on relevant technical aspects of the project

Briefly describe the method or approach used for the software design. If one or more formal/published methods were adopted or adapted, then include a reference to a more detailed description of these methods. If several methods were seriously considered, then each such method should be mentioned, along with a brief explanation of why all or part of it was used or not used.

The following are the requirements specification that can be incorporated (but not limited to) in this section : Functional Requirements

This section should describe what the system is to accomplish.

This should consist of a list, with the most important items at the top. These are the system capabilities that must be present in order for the client/user to carry out the services and features incorporated to it. It also includes how the system should respond to anticipated error conditions or invalid inputs. The requirement should be properly described. This will probably be a couple of lines explaining what you want to achieve. Make sure that you provide sufficient detail. Discuss also the importance of the requirement Requirements should be concise, complete, unambiguous, verifiable, and necessary.

 User Interfaces - Describe the logical

characteristics of each interface between the system and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed.

The following are the requirements .:

Hardware Interfaces - Describe the logical and

physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used

The following are the requirements .:

Software Interfaces - Describe the connections

between the system and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each.

The following are the requirements .:

Communications Interfaces - Describe the

requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms

Other Functional Requirements that may be included in the manuscript

Performance Requirements if there performance requirements for the product under various circumstances, state them here and explain their rationale Safety Requirements - Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the system. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Security Requirements - Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements.

System Overview
Provide a general description of the software

system including its functionality and matters related to the overall system and its design (perhaps including a discussion of the basic design approach or organization). Feel free to split this discussion up into subsections (and subsubsections, etc ...)

System Architecture
This section should provide a high-level overview of how the

functionality and responsibilities of the system were partitioned and then assigned to subsystems or components. The main purpose here is to gain a general understanding of how and why the system was decomposed, and how the individual parts work together to provide the desired functionality. At the top-most level, describe the major responsibilities that the software must undertake and the various roles that the system (or portions of the system) must play. Describe how the system was broken down into its components/subsystems (identifying each top-level component/subsystem and the roles/responsibilities assigned to it).

System Architecture (continued..)

Describe how the higher-level components collaborate with

each other in order to achieve the required results. Don't forget to provide some sort of rationale for choosing this particular decomposition of the system (perhaps discussing other proposed decompositions and why they were rejected). Feel free to make use of design patterns, either in describing parts of the architecture (in pattern format), or for referring to elements of the architecture that employ them. If there are any diagrams, models, flowcharts, documented scenarios or use-cases of the system behavior and/or structure, they may be included here Diagrams that describe a particular component or subsystem should be included within the particular subsection that describes that component or subsystem.

Other System Diagrams (if applicable) that maybe included:

Data Flow Diagram (DFD) Entity Relationship Diagram (ERD) Class Diagram

Corresponding discussion on the presented diagrams is necessary

Flowcharts (if necessary)

Discuss in this section how you are going to test the functionality, correctness and reliability of your developed system Present the result of the testing and evaluation of the project, for software development you may use any appropriate methods (alpha or beta test, smoke testetc) You may develop a questionnaire for the testing of your software. Let client (or target audience) and other users do some testing of your software. You can get comments on how user-friendly is your system and what recommendations they could give to enhance your project. Discuss with your adviser (or consultant/)s on the other criteria that you will use in the evaluation that you want to test. Decide on the number of people (respondents) that will do the testing and you can present a simple statistical computations to use.

This chapter will present the result of the development and testing of your system. Final design, interface, database, etc., can be presented here Results of test can be presented in tabulated or graph format (or both). Give your own analysis and views regarding the results

Make a conclusion on the efficiency of your system and give a summary of recommendations for its enhancement. You can give your own recommendations or you can base it from the comments of your users.