this PROJECT IS A PAYROLL SYSTEM
Abstract: (Required) Abstract is required. It is a summary of your project. Your final project report is expected to be 10 pages, including the references and title. The font is Times New Roman, the font size is 12. You may use multiple line space of 1.15 or 1.25. Do not use single space or double space. Please note: this instruction paragraph needs to be replaced with your work when you turn in your final report. I. Introduction Why do you want to do this work - goal and objectives. Background is to show the related work in this area. What are existing works in this area, what are current results? How do the current works solve the problem? Please put enough citation for current existing works in this area. Please note: this instruction paragraph needs to be replaced with your work when you turn in your final report. II. Design Model of System In this section, you need to present the model of the system. You need to use UML model (if you have no idea about any other design methodologies). In the UML model, the system design model must include static diagram - Class diagram and dynamic diagram. As in the midterm report, the class diagram and state diagram have been developed and included. (This won't be counted towards final report. Missing this part will be considered as incomplete report.) In the final report, other dynamic diagrams are required - use case diagram, sequence diagram and/or activity diagram. This is required for all projects. All content in the midterm report can be included in the final report. Please note, Your system design model must use the correct notation. Each design model needs to have one paragraph of description. Note: please replace these instruction paragraphs with your own design models when you submit your final report. III. System Implementation and Results All functions that you have implemented, new APIs (if you have), user defined classes, design patterns that you used, can be implementations. Make sure attach snapshots for your results. For each functions, show the key methods how this function is implemented, attach the code. You need to pay attention to followings: The implementation has to be consistent with design model; The implementation has to be consistent with the tasks defined in your document. IV. Software Testing Methodology Any system needs to be validated before release. The validation methodology can be software testing or formal verification. There are various types of testing technologies available now. A list of testing tool can be found in this link: https://ste-cyle.cis.fiu.edu/instances/. Please use the knowledge from the STEM-Cyle to validate your project. Other reference can be adopted and cited for your project report. A good reference book should be Roger S Pressman, "Software Engineering: A Practitioner's Approach," 7" edition, McGraw-Hill Science, ISBN-13: 978-007337597- 7. There are two unit testing techniques are recommended for this work: white box testing and black box testing. You are required to use one methodology, e.g., basis path testing. For Java applications, apps, you may use JUnit. For C or C-like program, you may use basis path testing. Testing is one of the biggest portion in the final report, please make sure you do it properly. Please note: the above instruction paragraph needs to be replaced with your work when you turn in your final report. VI. Conclusion This section is to summarize your work and conclude your experimental results. There are two main contributions of this project you may highlighted: First, a systematic modeling help developer to output high quality software systems in a clear and precise way; Second, a better understanding of the system model will provide efficient programming for the team by reducing the large amount of time in debugging, since it will help developers to find the problems and/or trace problems easily. Please note: the above instruction paragraph needs to be replaced with your work when you turn in your final report. Abstract: (Required) Abstract is required. It is a summary of your project. Your final project report is expected to be 10 pages, including the references and title. The font is Times New Roman, the font size is 12. You may use multiple line space of 1.15 or 1.25. Do not use single space or double space. Please note: this instruction paragraph needs to be replaced with your work when you turn in your final report. I. Introduction Why do you want to do this work - goal and objectives. Background is to show the related work in this area. What are existing works in this area, what are current results? How do the current works solve the problem? Please put enough citation for current existing works in this area. Please note: this instruction paragraph needs to be replaced with your work when you turn in your final report. II. Design Model of System In this section, you need to present the model of the system. You need to use UML model (if you have no idea about any other design methodologies). In the UML model, the system design model must include static diagram - Class diagram and dynamic diagram. As in the midterm report, the class diagram and state diagram have been developed and included. (This won't be counted towards final report. Missing this part will be considered as incomplete report.) In the final report, other dynamic diagrams are required - use case diagram, sequence diagram and/or activity diagram. This is required for all projects. All content in the midterm report can be included in the final report. Please note, Your system design model must use the correct notation. Each design model needs to have one paragraph of description. Note: please replace these instruction paragraphs with your own design models when you submit your final report. III. System Implementation and Results All functions that you have implemented, new APIs (if you have), user defined classes, design patterns that you used, can be implementations. Make sure attach snapshots for your results. For each functions, show the key methods how this function is implemented, attach the code. You need to pay attention to followings: The implementation has to be consistent with design model; The implementation has to be consistent with the tasks defined in your document. IV. Software Testing Methodology Any system needs to be validated before release. The validation methodology can be software testing or formal verification. There are various types of testing technologies available now. A list of testing tool can be found in this link: https://ste-cyle.cis.fiu.edu/instances/. Please use the knowledge from the STEM-Cyle to validate your project. Other reference can be adopted and cited for your project report. A good reference book should be Roger S Pressman, "Software Engineering: A Practitioner's Approach," 7" edition, McGraw-Hill Science, ISBN-13: 978-007337597- 7. There are two unit testing techniques are recommended for this work: white box testing and black box testing. You are required to use one methodology, e.g., basis path testing. For Java applications, apps, you may use JUnit. For C or C-like program, you may use basis path testing. Testing is one of the biggest portion in the final report, please make sure you do it properly. Please note: the above instruction paragraph needs to be replaced with your work when you turn in your final report. VI. Conclusion This section is to summarize your work and conclude your experimental results. There are two main contributions of this project you may highlighted: First, a systematic modeling help developer to output high quality software systems in a clear and precise way; Second, a better understanding of the system model will provide efficient programming for the team by reducing the large amount of time in debugging, since it will help developers to find the problems and/or trace problems easily. Please note: the above instruction paragraph needs to be replaced with your work when you turn in your final report
