The technology report should discuss your rationale for technology choices made for the project. It should be clear from your report that you considered standards and realistic constraints and used an engineering process to make technology choices for your project.
The technology report should include:
- An overview of the technology related issues.
- A list of requirements (functional and non-functional) for the technology to be used.
- A list of potential technology options.
- A set of strategies for evaluating your choices. This will likely include research as well as well chosen prototype implementations.
- Prototypes should be designed to help determine whether a particular technology will be best for your project. Typically these prototypes will focus attempting to create functionality for the least understood aspects of your project.
- A rationale for each technology choice listing advantages and disadvantages for each option considered. Be sure to including aspects such as cost and the potential for increased risk.
- Your target audience for this document is an ABET evaluator whose goal is to find evidence that you have
- defined the requirements
- identified potential technology
- developed relevant experiments and/or prototypes to increase your understanding of the technology
- identified and minimized risks associated with making specific selections
- clearly documented and justified your choices
- (b) an ability to design and conduct experiments, as well as to analyze and interpret data.
An ability to evaluate the performance of software systems, and to propose and evaluate process changes based on individual and team metrics.
- (c) an ability to design a system, component, or process to meet desired needs within realistic constraints such as economic, environmental, social, political, ethical, health and safety, manufacturability, and sustainability.
An ability to perform detailed and architectural design of software components and systems while satisfying functional and non-functional requirements.
- (e) an ability to identify, formulate, and solve engineering problems.
An ability to elicit and document software requirements, and to propose and evaluate designs and processes to meet them.
- (f) an understanding of professional and ethical responsibility.
An understanding of the critical role played by software systems, the professional responsibilities of software engineers, and ethical issues that may be encountered in engineering practice.
- (g) an ability to communicate effectively.
- (h) the broad education necessary to understand the impact of engineering solutions in a global, economic, environmental, and societal context.
- (i) a recognition of the need for, and an ability to engage in life-long learning.
- (j) a knowledge of contemporary issues. An awareness of trends in the software engineering discipline and of societal issues that affect software engineering practice.
- Your report will likely include summaries of experiments and/or prototypes as well as links to the raw data/code in GitHub/Bitbucket
Last modified: Wednesday, 27-Apr-2016 19:02:20 CDT