The document discusses the development of a 3D printing system to help architects and construction managers better explain building designs to clients. It outlines the waterfall project design methodology that will be used, which sequentially completes each phase before moving to the next. System requirements are also discussed, including minimum computer specifications needed to run the 3D software. Stakeholders are identified as programmers, customers, system designers, and consultants. The overall goal is to produce 3D printed models of building designs to make presentations more understandable for non-technical clients.

1. Running head: 3D PRINTING
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.

2. • 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

3. 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

4. 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.
1

5. Running head: 3D PRINTING
3D printing is a process of making three-dimensional objects
from a digital file. The creation of three-dimensional designs
utilizes additive processes. Printing of a 3D object is aa
process involving many steps (Vogt, B. 2016). The 3D printing
commences with the making of a virtual model of the subject
matter in mind. The object is in most cases a Computer Aided
Design (CAD) file. The CAD file is produced using a 3D
modeling application or with a 3D scanner to copy a preexisting
objects. The process of 3D printing involves two major
components 3D scanners and 3D modeling software.
3D scanners utilize different technologies to produce a 3D
model. These techniques include time-of-flight, structured or
modulated, volumetric scanning and much more. Today many
companies such as Google are implementing 3D scanning in
their hardware. 3D modeling software also comes I different
forms (Vogt, B. 2016). There is industrial grade software that
cost thousands of dollars per year. That is, you have to pay a
license for the license on a yearly basis. However, there is also
open sourced software like Blender.
The 3D is sliced first. Slicing is dividing the model into
hundreds or thousands of horizontal layers. Slicing is
performed using software for precision. In some 3D models, it
is possible to slice them from within the 3D modeling software
application. After slicing of 3D, the model is ready to be fed to
the 3D printer (Hiekata et al., 2016). A USB device, SD or Wi-
Fi is used to supply the data to the printer, but it all depends on
the type of printer in use. When a file is uploaded in a 3D
printer, the object is printed layer by layer. The printer reads
every slice which is a 2D image and creates a three-dimensional
object.
The main aim of the project is to produce 3D designs of
buildings. Architects and construction managers have noted
that it is tough to explain the model of a building to their
customers.

6. This problem is brought about by the fact that most of the
customers do not have the technical knowledge needed to
interpret drawings. Drawings are the commonly used form of
presentation (Hiekata et al., 2016). Multiple rejections and
measurements characterize these drawings. Through the 3D
models that are printed to scale, the technicians hope that their
presentations will become understandable even to the non-
technical minds.
The waterfall project design methodology is the most easily and
most implementable method in this design plan. The waterfall
model is a project management methodology based on the
sequential design process. Much like the waterfall that fills
lower levels with pools of water, the phases in the waterfall
model flow from one to the other. The waterfall model finishes
one phase before the next step begins. Waterfall methodology
applies to this project because the project is small and the
requirements of the project are determined upfront (Mahadevan
et al., 2015). A waterfall model has six phases namely:
requirements, design, implementation, verification deployment,
and maintenance.
The waterfall model requires that the requirements are
documented correctly before any other project work begins.
Therefore, the project manager spends more time in this phase.
The gathering of needs starts with the concept of what the
customer needs are. The manager discusses the idea with the
customers together with subject matter experts and other
stakeholders (Schubert et al., 2014). The project aims at
producing presentable 3D models of architectural structures for
its clients. The primary customers are home builders, architects
and everyone who is involved in the contracting business.
After the requirements stage, the project manager commences of
the system design. This phase is concerned with studying the
requirements and specifications stated in the first stage.
The stage helps in specifying hardware and system requirements
and also helps in defining the overall architecture of the
scheme. The logical design is an abstract representation of how

7. the software data flow, the inputs and the outputs. After full
completion of the plan, the team will review and approve the
design.
After approval of the 3D design then comes in the
implementation phase, this phase is concerned with building the
layout into the actual software. The 3D design that was
approved is then incorporated into the real software (Mahadevan
et al., 2015). The code is written, debugged and then tested.
During this stage, the programmers do the actual coding
according to the stipulated needs.
Once the functional and the non-functional testing is done, the
finished and tested product is launched into the customer base
(Mahadevan et al., 2015). The product is released to the market
for the customers to use it. Some complications come up after
the product initiation, here, the maintenance phase comes in.
These issues are mainly software related and not hardware
related. Therefore, to fix these problems, patches are released
into the market. Patches are just quick fixes to these
complications and take various forms. To enhance the
productivity of the system, then better versions are released to
the market. Maintenance is performed to deliver these changes
to the customer environment.
The waterfall model has various advantages, and they include:
• The arrangement of tasks in this model is comfortable.
• The documentation of processes and results in this model is
good.
• Also, the stages in the waterfall model are defined.
• Waterfall model works well for smaller projects such as this
one and requirements are well understood.
• In this model, the phases are processed and completed one at
a time.
Waterfall model also has its disadvantages, and they include:
• The model is not appropriate for a project whose
requirements are at a high risk of changing.
• When implementing the waterfall model, it is not easy to
measure the progress of stages.

8. • The model cannot accommodate changing requirements i.e.
the model is not flexible.
• The model is not appropriate for projects that take longer to
complete.
• Waterfall modeling also has high amounts of risk and
uncertainty.
The design input requirements must be documented, and the
specified conditions verified. A system must be tested and
validated before its presentation to the users (Mahadevan et al.,
2015). After the 3D system has been designed and
complemented, the system need be given to a group of users
who test it. The users verify that the 3D system works as
required and as stipulated.
The stakeholders of this project are the programmers,
customers, system designers, and consultants. The role of the
customers who are mainly people in the construction industry is
to provide the market with the product. The programmers, on
the other hand, are to write down the code of the 3D system or
what is commonly known as implementation. Consultants offer
technical advice to the team tasks with developing the system
e.g. software or system engineers. Users are also stakeholders in
the system the users are used in the testing of the scheme before
its release to the market. System designers provide information
about the system models.
Conceptual design stage of the scheme development
incorporates a team of consultants who go through the original
idea to solve the identified problem (Schubert et al., 2014).
The team outlines the specifications and a planning strategy.
Procurement and program phasing plan is also a matter of
concern at this stage. Various testing procedures are applied to
verify and validate the system.

9. 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.
Schubert, C., Van Langeveld, M. C., & Donoso, L. A. (2014).
Innovations in 3D printing: a 3D overview from optics to
organs. British Journal of Ophthalmology, 98(2), 159-161.
Vogt, B. (2016). CREATING THEORETICAL MODELS OF
VAULTS WITH THE USE OF AUTOCAD SOFTWARE, ON
THE EXAMPLE OF BARREL VAULTS. Technical
Transactions, (8).
1
Final Project Submission

10. Guidelines
3D PRINTING/PRINTERSSYSTEM
Purpose: This is the final project submission and should
represent a good initial draft of a “DESIGN MANAGEMENT
PLAN”. This will include material from the Milestone 1,
System Description and Milestone 2 submissions with some
additional information as outlined below.
The research paper should adhere to the following guidelines:
Due Date: August 4, 2017
Paper format:
· No more than 10 pages
· Margin: 1-inch on all sides.
· Spacing: Double-spaced.
· Font: 12
· Each page must be numbered
· The cover page must include the title, your name, course
number, course section, and the date of submission in APA
style.
Sources: Be sure to include references in APA style for
information supporting choice of design methodology,
stakeholder identification and management, design standards
and development of system level requirements.
Structure: The paper should have the following elements. This
may serve as an outline for your submission.
Introduction: The introduction should outline the operational or
customer needs that will inform and guide the design process.
It should also summarize the process of decomposing those
requirements to develop the system design baselines.
Design Planning: Planning for design management includes
selection of a design methodology, identification of relevant

11. standard & regulations, and determining the conceptual design
approach, as well as planning for stakeholder management.
This section will draw from material in Milestone 1.
Conceptual & Preliminary Design: Once the plan is laid out, the
system need and high-level requirements must be decomposed
into subsystem requirements for system synthesis, concept
evaluation and to define the system preliminary design. This
section will draw from material in Milestone 2.
Lower Level Design: The design manager must plan for lower-
level design processes to ultimately provide enough detail for
the system solution to be physically realized. Discuss the
different levels of lower level requirements and how they
contribute to the system specification. Describe the importance
of the final design review in design management.
System Evaluation: As the design process proceeds, the system
needs to be evaluated for conformance to requirements and
suitability for the stated need. Discuss verification and
validation in terms of design management planning. In
particular, describe the process for determining conformance
and suitability of the design solution.
Reference: In this section, cite any references in APA format.