Git Guidelines for Terminal Requirement
Git Guidelines for Terminal Requirement
Table of contents – Roadmap to each portion of the document, from the preliminaries to the
attachments. Use an automatic table of contents generated through MS Word
b. Business rules – Paragraphs detailing the rules and constraints of the business. Describes
the operations, and instructions on how certain day-to-day actions should be performed.
c. Business processes – Paragraphs detailing a collection of linked tasks which find their end in
the delivery of a service or product to a client. These are sets of activities and tasks that, once
completed, will accomplish an organizational goal. The business process discussed here should
be about the current system applied by the company.
Note: The business process and flowchart should focus on the problem areas of the company,
this may be done through observation or communication with the selected company via email,
telephone, or video conference. Face-to-face interaction is not mandatory.
a. Introduction
i. Business processes - (Discuss the business process of the current system applied by the
company. - Narrative form)
ii. Business process diagram - (A graphical representation of the steps discussed in the
previous section, i. Business processes, using the proper flowcharting symbols.)
iii. Assumptions and Dependencies - What are the current technologies used? What specific
technical assumptions do we need to know to understand how to design the proposed
change in the system? What are the dependencies that the company would need to
possess (such as factors or tasks that depend on the input of another factor) in order to
attain the change in the system?
a. Functional requirements - (What are the operational features of the proposed system?)
i. Input requirements
ii. Process requirements
iii. Output requirements
b. Non-functional requirements - (What are the qualitative features of the proposed system,
aimed to make it usable and effective for the users?)
i. Performance requirements - (What are the features of the system that enhance
customer satisfaction?)
ii. Security requirements - (What security controls are needed to safeguard and protect the
system from cyber threats?)
c. Business process model and notation - Detailed graphical representation of the improved
business processes. (This graph would be similar to that of the ii. Business Process Diagram in Chapter II,
but the enhancement of the process with the use of the Proposed System will checked here.)
d. Feasibility - Analysis that considers all of a project's relevant factors to ascertain the
likelihood of successfully completing the project. (Discuss the Pros and Cons of undertaking a project
before investing a lot of time and money.)
i. economic
ii. technical
iii. operational
iv. scheduling considerations
e. The Prototype – A prototype is a rudimentary working model of a product or information
system, usually built for demonstration purposes or as part of the development process. A basic version
of the system is built, tested, and then reworked as necessary until an acceptable prototype is finally
achieved from which the complete system can now be developed. Several different platforms may be
utilized for the development of a prototype but this should include the user interface design and the
outputs or reports generated by the system.
The Conclusions and Recommendations may be combined or, in long reports, presented in
separate sections. If there are no recommendations to be made as a result of the research, just call this
section Conclusions. The Conclusions section sums up the key points of your research, the essential
features of your design, or the significant outcomes of your investigation. As its function is to round off
the story of your project, it should: be written to relate directly to the aims of the project as stated in
the Introduction, indicate the extent to which the aims have been achieved, summarizes the key
findings, outcomes or information in your report, acknowledges limitations and makes
recommendations for future work (where applicable), and highlight the significance or usefulness of
your work.
Bibliography – A bibliography is a list of all of the sources you have used (whether referenced or not) in
the process of researching your work. In general, a bibliography should include the authors' names, the
titles of the works, and the names and locations of the companies that published your copies of the
sources. Separate resources style appropriately, and arrange alphabetically.
Appendices – Appendices contain material that is too detailed to include in the main report, such as
long calculations, detailed technical drawings, tables of raw data, communication letters, interview
questions, and photo documentation. The content should be summarized and referred to at the
appropriate point in the body of the report.