Implementation, Systems Development:  

Systems Home | Introduction | Needs Assessment | Requirements Specification | Requirements Analysis | Preliminary Design | Detailed Design | Implementation | Testing

Systems Development: Requirements, Design, Implementation, Testing

Implementation

We know what system to build. We know how to build it. Eventually we will determine if the system was built correctly. What task remains? Build the system!

While previous units had both practice and theory, this unit is almost all practice. It is a true work of synthesis, not analysis. We have spent our time up to this point in analysis, or breaking down a theoretical system into smaller pieces. We now must shift to synthesis, or taking these theoretical pieces and building a practical system.

Process Activities

When we finished detailed design, we ended with a blueprint for the system components: forms, logic, and tables. Now we take those blueprints and "cut metal," or convert from specification to product.

While building, we need to worry about elements of style. With natural languages, there are a number of conventions that do not influence meaning, but do make a work easier to read. These include punctuation and usage that appear only on the printed page, not in verbal speech.

Likewise with computer code, there are conventions that do not impact the meaning interpreted by the compiler, but do make code easier for people to understand. These conventions are called coding standards. Before we start building, we will adopt a set of standards specifically for this project.

Exercise

Our assignment is rather simple: build the system.

Coding Example

Most Access development is done through the user interface: point and click to design forms and reports. But sometimes we must write Visual Basic code associated with form controls to accomplish specific tasks. Here is a sample application that demonstrates how to attach code to control events:

Study Guides

There is no study guide for this unit. No quiz, either!

Lecture Slides

Here are copies of the lecture slides presented during class:

Readings

Each of the listed links will open a new browser window:

Concept Notes Links
Definitions Here are some basic articles about topics which are fundamental to this unit.

Programming style: A Wikipedia article.

Naming conventions (programming): A Wikipedia article.

Visual Basic Coding Conventions Here are the formal coding conventions Microsoft recommends for use with the visual basic language.

Visual Basic Coding Conventions: Microsoft Developer Network.

Serious Parodies There are two articles circulating on the Internet with the same title. Both are "tongue in cheek," but raise serious issues on how NOT to write source code. Doing the exact opposite of what these two articles suggest is in fact excellent practice.

How To Write Unmaintainable Code: Roedy Green, Canadian Mind Products. The more popular of the two different versions.

How To Write Unmaintainable Code: Mark Detting, University of Ulm. This version has the same introductory paragraph, but the examples are completely different.

Systems Home | Introduction | Needs Assessment | Requirements Specification | Requirements Analysis | Preliminary Design | Detailed Design | Implementation | Testing


Copyright ©2006-2009, Jason Paul Kazarian. All Rights Reserved. License for reproduction, derivative works, internal commercial, and external non-commercial use granted to GITC faculty, staff, and students.