CS630 Final Research Report Or Q&A (800 Points Max)

CS630 Final Research Report or Q/A (800 points max.)

The final research report is due by 05/31/2020. Late submissions will not be accepted. Submissions must be uploaded in the designated Moodle portal; physical copies or email submissions are not permitted. Each student may select only one of two options: Option 1 involves creating a research report on a topic related to Software Engineering, suitable as a foundation for a Master’s Thesis or Dissertation. Option 2 involves preparing a question and answer bank based on assigned course materials, which can be expanded in future terms. The research report must adhere to specific structural and formatting guidelines outlined in the CU Research Guide, including APA style, length, and citation standards.

Paper For Above instruction

Option 1: Research Report / Individual Project

Students opting for this path must develop a scholarly research report centered on a topic within Software Engineering. Eligible topics include: Software Engineering and UML, Cloud Computing (Intranet or Extranet), Software Security, Machine Learning, Artificial Intelligence, or design of computing technologies such as processor design or networking. The report must be at least 3,500 words, supported by at least five peer-reviewed journal articles. The structure must consist of five chapters: Introduction, Literature Review, Methodology, Findings and Results, and Conclusions with Future Recommendations.

In the Introduction, clearly present the context, problem statement, goals, research questions, relevance, significance, and barriers. Conduct a comprehensive Literature Review, critically evaluating existing knowledge and identifying gaps. The Methodology chapter should detail the analysis approach, preferably comparative or advantage/disadvantage analysis. The Findings chapter will objectively report results, supported by necessary figures or tables in the Appendices. The Conclusions chapter should articulate how well objectives were met, implications for the field, limitations, and recommendations for further research or practice.

The report must follow APA formatting for citations and references, with double-spacing, 1-inch margins, Times New Roman 12-point font, and proper heading levels. The document should include a title page with the report’s title, submission date, team name, and members’ names. Proper academic language proficiency is expected. The final report must be a minimum of 15 pages of content, excluding appendices, with all materials from peer-reviewed sources. The submission format is exclusively Microsoft Word (.doc or .docx).

Option 2: Question / Answer Bank

Choosing this option requires creating a comprehensive set of questions and answers derived from assigned course materials, including textbook chapters, PPTs, and discussion forums. At minimum, produce 10 questions per chapter for chapters 1 through 14, resulting in at least 140 questions. These questions must encompass multiple-choice (MC), fill-in (FI), multiple-answer (MA), and essay (ES) formats, with only one short quotation per page. An additional essay question with an answer is required for each chapter. Questions and answers must be original, demonstrating understanding without copying from sources, and should be checked against plagiarism.

The question set should include clear chapter and question identifiers (e.g., Ch01Q01), and the correct answers should be highlighted or indicated accordingly. Questions should be relevant, accurate, and aligned with the assigned course content.

Paper For Above instruction

For the research report, the student will select a relevant topic within Software Engineering and develop a comprehensive, scholarly paper following the structured chapters outlined. The introduction will establish the context and articulate the problem statement, emphasizing its importance and scope. The literature review will examine existing research, highlighting gaps and rationale for the current study. Methodology will involve a comparative analysis or critical evaluation approach suitable for the research questions. Findings will present analyzed data, results, and insights, with possible supporting figures in the appendices. The conclusion will synthesize the research outcomes, discuss implications, and propose future research directions or practice improvements.

In creating the question and answer bank, students will thoroughly review assigned materials, generate a wide array of questions across multiple formats, and supply accurate, well-explained answers. The questions will reinforce understanding of key concepts, definitions, processes, and frameworks within the discipline, helping to prepare for assessments or to expand the course's question pool for future use.

References

  • Bass, L., Clements, P., & Kazman, R. (2012). Software architecture in practice (3rd ed.). Addison-Wesley.
  • Boehm, B. (1988). A spiral model of software development and enhancement. Computer, 21(5), 61-72.
  • Pressman, R. S. (2014). Software engineering: A practitioner's approach (8th ed.). McGraw-Hill Education.
  • Schach, S. R. (2007). Classical and object-oriented software engineering. McGraw-Hill Science/Engineering/Math.
  • Fowler, M. (2003). Refactoring: Improving the design of existing code. Addison-Wesley.
  • ISO/IEC/IEEE 42010:2011. Systems and software engineering — Architecture description.
  • Sei, T., & Morch, A. (2002). Understanding software security. IEEE Software, 19(3), 54-61.
  • Wegner, P. (2000). Software design and decomposition. IEEE Software, 17(4), 94-96.
  • McConnell, S. (2004). Code complete: A practical handbook of software construction. Microsoft Press.
  • Jorgensen, M. (2013). Software testing: A craftsman's approach. CRC Press.

Related Assignments