Software engineering

This project will facilitate the creation of the SpaceX dual flight interface for space faring shuttles and/or similar vehicles. The interface will have two distinct physical representations: a large, semitransparent glass display that serves as the craft’s main controls, and a smaller handheld pad-like display. The two displays will be mirrored to one another updating simultaneously, and connected remotely. Finally, this interface will connect to and control all onboard vehicle functions, such as navigation, engine control, internal systems, communications, database, etc., and will have easy access plug-in control for new applications to be added to the ship’s system.

1. The SpaceX interface is to be installed on high altitude and spacefaring craft. Due to the inherent danger of traveling in these situations, the SpaceX interface system shall pass with a 100% rating before being deployed in any ship system.

2. The visible portion of the SpaceX interface is a GUI, and as such shall be accessible to individuals with differing languages, as well as with easy to understand icons and menus.

3. For every craft the SpaceX interface is installed on, there shall be available at least one copy of the user manual document with full instructions on the operation of the SpaceX interface.

4. The SpaceX interface shall have the ability to function on minimal power, to avoid the danger of power failure within the host craft.

FDD

Feature Driven Development is part of the family of agile development methods. Specifically, FDD works by breaking the project into work segments based on primary features that will be present in the system. “A feature is a small, client-valued function expressed in the form <action><result><object>.”

(Ambler, 2014)

Working in this manner allows work segments to be reviewed as they are completed, allowing for reallocation of resources as they become available to finish the project within budget and on time.

As with all agile development models, FDD reduces time spent on redundant or irrelevant processes and documentation by allowing decisions to be made within the work sections, while still having a system of progress review. Furthermore, each section has enough autonomy to adapt to changes in situation such as team or policy change, presumably only affecting the rest of the project minimally or not at all.

Finally, agile models encourage the reuse of pre-existing codes or systems to reduce development time, while not breaking any content laws.

Justification

Using FDD as the development method has numerous advantages for the SpaceX interface project. The shortened time to completion inherent to agile development is attractive for this project, as having exceptional and safer systems available in high-altitude and space-faring vehicles is ideal. In addition, because of the urgency and resources involved, the available project team will be experienced enough to handle the type of work necessary with FDD.

The abundance of distinct components to the SpaceX interface lends itself to the FDD model; including primary GUI, mobile GUI, remote connection, and universal module control (this is what allows the GUI to interface and affect all other onboard vehicle systems). Furthermore, some of these components will have reduced timeframes as technology for GUI’s and remote control already exist, and will mostly need to be individualized and made to fit specific hardware.

Finally, the building of the universal module control component means that the project will be able to draw on the code for pre-existing ship systems, and not have to create new programs for every single physical part of the ship (making best use of available resources).

Ambler, Scott W. (2014). Feature Driven Development (FDD) and Agile Modeling. Retrieved from: http://agilemodeling.com/essays/fdd.htm

CTU (2017). M.U.S.E.: Software Engineering Methodology. Retrieved from: https://class.ctuonline.edu/_layouts/MUSEViewer/MUSE.aspx?mid=9464413