Читать книгу Artificial Intelligence for Business - Jason L. Anderson - Страница 16

With a successful prototype under your belt, you have been able to see the value of the technology in action. Now it is time to further invest and complete your system. At this point, it is also a good idea to revisit your user stories and plan as a whole to determine if any priorities have changed. You can then proceed with building the production system.

The production step is the process of converting the prototype into a full-fledged system. This includes conducting a technological evaluation, building user security models, and establishing testing frameworks.

 Technological EvaluationDuring the prototype phase, developers select technologies appropriate for a prototype, including using technologies and languages that are easy to work with. This mitigates risk by determining the project's feasibility quickly before investing a lot of time and money. That said, during the production step the technology must be evaluated for other factors as well. For instance, will the technology scale to a large number of users or massive amounts of data? Will the technology be supported in the long term and be flexible enough to change as requirements do? If not, pieces of the prototype might have to be rebuilt to accommodate.User/Security Model

 During the prototype phase, the project is typically only running on locked-down development machines or internal servers. While they require some security, high levels of security are not typically needed during prototyping and will only slow down the prototyping process. Work, such as integrating an organization's user directory (single sign-on [SSO]) and permission structures, will be part of the production process.Testing Frameworks

 To ensure code quality, testing frameworks should be built alongside the production code. Testing ensures that the code base does not regress as new code is added. Development teams may even adopt a “test first” approach called test-driven development (TDD) to ensure that all pieces of code have tests written before starting their implementation. If TDD is used, developers repeat very short development cycles, writing only enough code for the tests to pass. In this way, tests reflect the desired functionality and code is written to implement that functionality.