Reference no: EM131476205

Software Engineering Methodologies Assignment - Individual Roots of Polynomials - Quadratic

Overview -

This assignment requires you to analyse a problem and to design a solution (without any programming), which the user interacts with, via a GUI. The tasks required of your program will require you to demonstrate your understanding of the concepts covered in Weeks 1-3 of the course setting the foundations and a brief introduction to the course.

Learning Outcomes Assessed -

• Critically analyse and use complex decision making to research and determine the appropriate Software Engineering tools and methodologies to utilize in a given situation.
• Apply professional communication skills to support and manage the engineering of a large software system.
• Review, critically analyse and develop artefacts to define processes for quality assurance, risk management and communication in large software development projects.
• Implement quality assurance activities in order to verify user requirements and validate design decisions.
• Analysis of a large system development problem to decide upon the best methodological approach.

Assessment Details

The application of quadratic equations is boundless; examples that spring to mind are parabolic paths of projectile motion, velocity in a gravitational field, optimization of profit/loss, and the golden ratio being just a few.

In this task you are required to design a user interface for the solution of quadratic equations. The quadratic solutions should be clearly shown as well as proof that they do solve the quadratic equation. Feedback should be given to the user if invalid data is entered.

Analysis

The following analyses should be completed at the commencement of this project:

• User Analysis - who will be using the system?
• Display Content Analysis - what needs to be displayed?
• Work Environment Analysis - what is the platform/environment/architecture?
• Interface Design Steps - what are the interface objects and actions?

Refer to Pressman's chapters on Interface Design as well as Hix and Hartson.

After these analyses have been completed, you should decide on the software tools which you will use. Justify these in your report.

For example, for the graphics you might choose from: Microsoft Word (using the SmartArt, Shapes, Pictures features), Microsoft Paint, Microsoft Powerpoint, GIMP (www.gimp.org), Adobe Acrobat, Enterprise Architect (EA), Inkscape (www.inkscape.org), Photoshop, Paint.net or possibly from Web Tools such as Dreamweaver. Justify your choices in your report.

You will need to model the application; you may choose any model discussed in lectures such as DFD, FSM, SASD, ERD, CSPEC and justify your choice of model or combination of models. Demonstrate the usefulness of your modelling.

You will need to provide a State Chart Diagram (State Transition Diagram) of your application as well.

As there is no programming required in this assignment, you are encouraged - but not obliged - to use Wolfram|Alpha to solve your quadratic equations. Wolfram|Alpha is a free-form input computational knowledge engine using natural language. For example you could type "2 + 3" or "what is 2 + 3?" or "what is the sum of 2 + 3".

Your GUI should appear to be solving the equations and you may use any relevant output generated from Wolfram|Alpha in your GUI.

Requirements -

1. Your application must provide the user with all roots of a representative set of quadratic equations of the form

y(x) = ax² + bx + c

You will need to create your own set of equations; state why you chose them and why they are needed to show that the application is working correctly.

For example, it must produce solutions to equations of the type:

y(x) = x² + 1

y(x) = x² - 4x + 3

y(x) = 3.5x² + 5.5x + 11.5

and any variations thereof.

1. The equation to be solved must be displayed to the user in a suitable form

2. The solutions must be presented in graphical and numerical form.

3. The solutions should be presented in graphical and numerical form and must be shown to be correct.

4. The interface must be designed according to best practice and aesthetics.

5. The user must be made aware of any invalid data entered.

Suggested References:

Pressman, R. S. (2010). Software Engineering: A Practitioner's Approach (7th Ed.)New York, USA: McGraw-Hill.

Hix, D., & Hartson, H. R. (1993). Developing user interfaces: Ensuring usability through product and process. New York, U.S.A: John Wiley & Sons.