See attachment, assistance requested

The development of the 3D system will make use of the waterfall methodology (Hiekata et al., 2016). The sole aim of the system is to solve a problem realized by architects and other technicians involved in the building and construction industry. The engineers noted that after all their presentations their clients were still left with numerous questions. During their presentations, the architects use technical drawing to explain how the design of the building under construction will look. Therefore, anyone without any prior technical knowledge about these drawings will not fully understand what the architects will be taking about. Most of their customers do not have technical expertise concerning construction. It is therefore hard for the technicians to explain to their clients the reasons for the costs. The project utilizes the waterfall methodology because it is easily implementable in such a system. The waterfall method uses the notion of completing one task or phase before commencing the next step. The methodology relates to the actual waterfall which first fills the lower pools with water before the water trickles down to other pools below them. The computer that will be used to run this system should have the following minimum requirements:

• The CPU should be a dual core 1.8 GHz

• The computer should have 1GB RAM.

• The operating system should be Windows 7.

• The computer should have a video card of 512MB.

• Finally, the computer should have 500MB in free disk space after installation.

However, for this system to run smoothly on the computer these are the recommended system requirements:

• The computer should have a dual core processor of 2.66GHZ.

• The computer should have 2GB RAM.

• The computer should have a 1GB video card.

• The computer should also have 1GB in free disk space after installation of the 3D software.

A functional baseline is an in-depth description of the functionalities of the system. It describes the interface and operational characteristics of the system. It also stipulates what needs to be done for these functional characteristics to be achieved (Hiekata et al., 2016). The system and software specifications indicate the requirements required for a computer to run particular software. In this case, the system requirements will stipulate the demands of the equipment both hardware and software to run the 3D software. The software will be rendered incomplete without the system and software requirements. The system specifications play significant roles and have their corresponding benefits. For instance, the system specifications establish an agreement between the clients and the developers on what the software is supposed to do. The system specifications also save time for the developers. Since they are developed at the start of the project, the software engineers will not be forced to redesign their work after realizing they have not met their goal. An organization can transfer software to its various departments due to the existence of the system requirements and specifications. In developing the system needs of the project, the following considerations will be in place:

1. The functionality of the scheme. This addresses what the 3D system is supposed to do. The system is expected to print out 3D building models for architects to help them in their presentations.

2. The external interfaces. This addresses the question of the required add-ons or hardware for the working of the system. For instance, the system is not complete without the presence of a 3D printer connected to the computer. This step also stipulates how the software is supposed to interact with the users. Therefore, the hardware and software functionalities are defined.

3. The attributes of the software. Here, the process of maintenance of the software is stipulated, how long it takes to update the software, the portability of the system and how to securely store the system.

4. The design constraints.

5. The installation drawings and instructions.

6. Consideration of the needs of the stakeholders and users in developing the specifications.

A proper system requirement and specification document should be verifiable. Unambiguous, complete and consistent to say the least.

Subsystem requirements stipulate the needs or requirements for each subsystem and the followed ways so that the specified needs are met. These requirements are drawn up by establishing the resources the 3D system will mostly be utilizing. For the system to perform correctly, the processor must have a minimum of Pentium 4 or AMD Athlon 64. The recommended processor, however, is an Intel Core 2 or better. The operating system must be Windows 7 or higher which can either be 32 or 64-bit based. The 64-bit based operating system is much better and recommended because the analysis engine utilizes more than 4GB. The system will run smoothly and efficiently thus solving larger problems (Mahadevan et al., 2015).

The video card should have a minimum resolution of 1028 by 768 and 16-bit colors. For better quality in graphics, the device should support legacy depth bias. The RAM of the device should be at least 4GB for a 32-bit based device and 8GB or higher for a device running on a 64bit-based operating system. The hard disk drive (HDD) on the computer should be a minimum of 500GB. However, a larger HDD is better because more space is available for the running and storage of 3D model files. There is also more room to store analysis results (Mahadevan et al., 2015).

The preliminary design is the initial stage in any design process. It involves the coordination of both the users and the design team in a bid to collect information. A series of meetings are organized where the users are asked to specify their needs or requirements. The work of the development team is to note the needs of the_14 users and carry out research in the field so as to meet these demands. The team carries out research by first analyzing pre-existing solutions to the needs of these users. The information collected is analyzed, and it is determined whether it will have any impact on the project. Before passing, the data is analyzed by all stakeholders and then fine-tuned. The preliminary design defines the overall layout of the system.

References

Development Architecture Comparison of Waterfall and Agile Using Reliability Growth Model. In ISPE TE (pp. 471-480).

Hiekata, K., Mitsuyuki, T., Goto, T., & Moser, B. R. (2016, October). Design of Software

Mahadevan, L., Kettinger, W. J., & Meservy, T. O. (2015). Running on Hybrid: Control Changes when Introducing an Agile Methodology in a Traditional" Waterfall" System Development Environment. CAIS, 36, 5.