ITEC-2050 Systems Design
(UML)
Domain Class Diagram examples:
Class Responsibility Collaboration Cards Example:
|
|
Hierarchical Architectural Arrangements in Systems Design | |
File Size: | 22 kb |
File Type: | docx |
Excerpt: Hierarchical arrangements are those where by the entire structure is in the shape of a pyramid. The lower components report to upper components, until there is one component remaining. In systems analysis and design, these portions would be made up of programmatic modules, whereby, each successive step down the pyramid is more finely detailed and closer to the programming base layer than the last. Such hierarchical arrangements lend themselves to some system architectures, while others tend to flounder or are simply incompatible with this setup.
Web Hosted Infrastructure | |
File Size: | 21 kb |
File Type: | docx |
Excerpt: Personally, I have no qualms with using web hosted infrastructure (hate the term cloud as it has been taken over by the media to mean something different). It is a fast, easy, well managed way to get enterprise level structured systems connected to the internet, generally with the same skills as it would take to do it locally. This means there is no loss of jobs from losing skilled individuals. However, in some instances staff may be forced to take new roles.
Dental Clinic System | |
File Size: | 135 kb |
File Type: | docx |
Excerpt: Before I created either the Domain Model Class Diagram (DMCD) or the Domain Class Diagram (DCD) I created a use case scenario and use case descriptions for the entire use case as outlined in the assignment. In this way, I was better able to understand what classes would be needed. The Domain Model Class Diagram (DMCD) shows only those classes which are in the problem domain for the Dental Clinic System use case, along with the relations between those classes. I treated the DMCD as a kind of mini first draft DCD for the final push. As such it is more of a design level DMCD rather than analysis level DMCD.
Design Patterns | |
File Size: | 21 kb |
File Type: | docx |
Excerpt: Decorator Pattern and Proxy Pattern are both offshoots of the Adapter Pattern. Both patterns are similar in that they wrap an object thereby acting as a layer of indirection. However, each performs a slightly different function to that of the Adapter pattern, and to each other.
Accounts Payable System and Data Input Integrity | |
File Size: | 21 kb |
File Type: | docx |
Excerpt: An accounts payable clerk is responsible for the management and maintenance of outgoing funds from an organization. Without appropriate security and validation measures, this one position could lead to a monetary black hole that could wipe out an organization. As such, the integrity controls of a check writing system needs to be both robust and secure. In total, the system needs to check for valid input, authorized access, and control output authorization and locations (Satzinger, Jackson, & Burd, 2012, pp. 393-395).
E-Commerce Site Security | |
File Size: | 21 kb |
File Type: | docx |
Excerpt: The site I chose to analyze was Amazon.com (Amazon.com, Inc., 2012). This site is one of the few e-commerce sites I frequent on a regular occasion. As such, it seemed like the perfect choice for penetration testing. Amazon has implemented several layers of security (which I am thankful for) which include, but are not exclusive to: HTTPS, security certificates, data encryption, and TSL data transmission.
Billing System Upgrade and Data Integrity | |
File Size: | 22 kb |
File Type: | docx |
Excerpt: The HudsonBanc billing system upgrade had the potential to bring in large amounts of revenue and performance upgrades without drastically changing how the company operated as a whole (Satzinger, Jackson, & Burd, 2012, p. 439). However, due to mismanagement of the system upgrade the whole process was botched. Their project planning and upgrade procedures are a great example of how not to do a system change over.
SDLC Methodologies | |
File Size: | 20 kb |
File Type: | docx |
Excerpt: While the Unified Process and Agile Methodologies are both exceptionally resourceful, they are only ideal when working on projects which can be rolled out through multiple iterations. When working on a project that must be completed within one iteration, both of these methodologies fall flat on their face. This is because they are both setup to take advantage of the iterative approach to SDLC.
Comment Box is loading comments...