Reference no: EM133121833

ISE102 Introduction to Software Engineering

Learning Outcome 1: Utilise an integrated development environment to develop practical software project solutions.

Learning Outcome 2: Demonstrate the ability to read and interpret code, describe its purpose and systematically debug for issues in syntax or logic.

Learning Outcome 3: Utilise an industry standard programming language to solve simple application design problems.

Learning Outcome 4: Demonstrate a foundational understanding of procedural programming and modular design.

Assessment Task

Display your understanding of modular design principles and knowledge of C++ language features learned in Modules 5-8 to diagnose and solve problems in the provided modular software project. Follow the steps provided in the Instructions to improve the program. Add extended features, either suggested or your own.

Please refer to the Task Instructions below for details on how to complete the sub-tasks.

Context

In Assessment 1 you applied and explained the variables, expressions, conditionals and loops that make a computer so powerful and flexible. Assessment 2 requires you to apply knowledge of functions, their arguments, return values and concepts of modular design to begin building larger, more capable programs. This marks the start of your journey towards full blown games, apps and systems software, and of building confidence in your own ability to break down problems and design solutions.

Instructions

A program, like any real-world task, runs over time. It starts, it progresses, and it will eventually end. Along the way we find ourselves in different stages of that task. This abstract idea comes to life in role-play and adventure games; quests take you on a journey through various locations, encountering creatures and puzzles, collecting and maybe crafting things along the way.

In this assessment, you are the inheritor of such an adventure: a C++ project called "Adventure". This game project was started by another programmer, but there's plenty to be done. Your task will be to understand and then complete it. Questions you will ask yourself include: What was it intended to do? Does the code work? How will players choose what to do, and how will you keep track of progress through the quest?

Your Learning Facilitator will provide you with the code project in Module 6. You will partly explore and work on the code in class before continuing on your own. You will be applying the principles and skills you learn throughout the modules, leveraging and demonstrating your learning.

1. Read the comment at the top of the project's main source file for an overview of your tasks.
2. For tasks that have to be coded in particular locations in the code, you can search for comments beginning with // TODO:
3. Other, more general tasks, will require you to decide what code to write and where. Tasks you'll encounter include:
• Creating custom functions with arguments (inputs) and return values (outputs)
• Keeping track of the state of the program
• Communicating the state of the program - if the user doesn't know it's happening, it isn't happening! Formatting output clearly and with characters using fmt, handling bad input gracefully and with useful errors.
• Designing for maintainability and reduction of bugs: make the code modular by reducing use of global variables, and only expose functions to as much information as they need to do their job.

Referencing
It is essential that you use appropriate APA style for citing and referencing research.

Attachment:- Software Engineering.rar