Software Engineer Report

25
Software Engineer Report What should contains the report?!

description

Software Engineer Report . What should contains the report?!. Report Head Outline. Cover page Abstract Acknowledgments Table of content Table of figure Table index . Chapter outline . Chapter 1: Introduction Chapter 2 : Literature review Chapter 3: Project management - PowerPoint PPT Presentation

Transcript of Software Engineer Report

Page 1: Software Engineer Report

Software Engineer Report

What should contains the report?!

Page 2: Software Engineer Report

Report Head Outline Cover page Abstract Acknowledgments Table of content Table of figure Table index

Page 3: Software Engineer Report

Chapter outline Chapter 1: Introduction Chapter 2 : Literature review Chapter 3: Project management Chapter 4 : SRS Document Chapter 5: Software Design Chapter 6: Implementation Chapter 7: Testing Chapter 8 : Conclusion & Future work

Page 4: Software Engineer Report

Report Tail outline Abbreviation Appendix References

Page 5: Software Engineer Report

Abstract Summarize of research article / thesis , review

, project ..etc. The abstract have to talk about

Natural of your project Its context How it was carried out What its major finding are

After you done of the abstract , test it by the following questions : What you have achieved ?? What the content of your dissertation ??

Page 6: Software Engineer Report

Acknowledgments Where you express thanks to those who have

provided to you help either Academic guidance or material contribution to you .

Page 7: Software Engineer Report

Table of contents

Page 8: Software Engineer Report

Table of Figure

Page 9: Software Engineer Report

Table of tables

Page 10: Software Engineer Report

Chapter 1 : Introduction Chapter is going to describe briefly what your

project is about will define the scope of your project. You are going to talk about problem area

briefly Finally you write roadmap of project report for

example : In chapter 2 we are going to talk about …. , while in chapter 3 we will discuss …

Page 11: Software Engineer Report

Introduction can be divide into Introduction Background Problem definition Project objective Road map

Page 12: Software Engineer Report

Literature Review Chapter where you review the critical points of

current knowledge on a particular topic. Critical examination of relevant theories / concepts ,

approaches method and techniques. You need talk about how and where you will have

used any of the results of your literature study in your project. Provide an understanding of the topic area problem domain / technology – in terms of established theory and practical

Also , demonstrate that you can apply knowledge that you have been expose to .

In addition , reuse tried and tested ideas , methods and technique

Page 13: Software Engineer Report

Division Introduction Background Other section depend own your project need

Page 14: Software Engineer Report

Chapter 3 : Project management Task analysis State how traditional phase of a software

development life cycle form part of an academic development project

Describe typical documentation of each stage

Page 15: Software Engineer Report

Chapter 3 : Division Introduction Software process model Risk management

Overview Process description

Feasibility study Project activities and plan

Page 16: Software Engineer Report

Chapter 4: SRS Introduction Requirement collection Requirement analysis

Functional Non-functional

DFD Process specification Structure English Decision table Decision tree

Page 17: Software Engineer Report

Chapter 5 : Software Design Introduction Design database Design Screen / layout / wireframe Design Database Design dictionary Design data flow Data structure STD

Page 18: Software Engineer Report

Implementation & Testing Introduction Testing type

Page 19: Software Engineer Report

Chapter 8 : Conclusion and future work Final words in your project should be logical

and from the work carried out. Include an assessment of the complete

product Also , be critically assessing the work that has

been carried out Propose any recommendations for extending

the work as future work

Page 20: Software Engineer Report

You may divided into Objective Benefit Problem encounter Future work

Page 21: Software Engineer Report

Abbreviation This section contains a list of standard word

abbreviations. In some cases, several words may share the same abbreviation. Usually, other parts of the object name will help place the abbreviation in context.

Any words/abbreviations with an asterisk (*) are from PeopleSoft's standards. PeopleSoft object names using any of the words listed below MUST use the indicated abbreviation.

Page 22: Software Engineer Report
Page 23: Software Engineer Report

Appendix An addendum/Appendix, in general, is an addition to

a certain document, sometimes subsequent to its edition, publication or diffusion.

In a book, an addendum (sometimes referred to as an "appendix") is a supplemental addition to a given main work. It may correct errors, explain inconsistencies or otherwise detail or update the information found in the main work, especially if any such problems were detected too late to correct the main work. For example, the main work could have had already been printed and the cost of destroying the batch and reprinting is deemed too high. As such, addenda may come in many forms — a separate letter included with the work, text files on a digital medium, or any similar carrier.

Page 24: Software Engineer Report

References Bibliographies are special reference works

that are used to identify as many published works on a given subject as possible, and serve as compilations for other authors or researchers.

Page 25: Software Engineer Report