...Template for IDA Project (Project Id) Template for specific development (Contract Id) Technical Design Document Issue 1 TABLE OF CONTENTS 0 Preface 1 0.1 PURPOSE OF THIS DOCUMENT 1 0.2 Use of this document 1 0.3 Overview 2 0.4 Basis of this Document 2 0.5 A Reference Architecture for the IDA Programme 3 0.6 Specific Design Considerations 3 1 Introduction 5 1.1 PURPOSE 5 1.2 Scope 5 1.3 Definitions, Acronyms and Abbreviations 5 1.4 References 6 1.5 Overview 6 2 System Overview 7 2.1 SYSTEM CHARACTERISTICS 7 2.2 System Architecture 7 2.3 Infrastructure Services 9 3 System Context 10 4 SYSTEM DESIGN 11 4.1 DESIGN METHOD AND STANDARDS 11 4.2 Documentation Standards 12 4.3 Naming conventions 13 4.4 Programming Standards 13 4.5 Software development tools 13 4.6 Outstanding Issues 14 4.7 Decomposition Description 14 5 Component Description 15 5.1 COMPONENT IDENTIFIER 16 6 Software Requirements Traceability Matrix 19 DOCUMENT CONTROL 20 DOCUMENT SIGNOFF 20 DOCUMENT CHANGE RECORD 20 0 PREFACE 0.1 PURPOSE OF THIS DOCUMENT 1. THIS DOCUMENT IS A GENERIC TECHNICAL DESIGN DOCUMENT DOCUMENT FOR USE BY IDA PROJECTS. IT PROVIDES GUIDANCE AND TEMPLATE MATERIAL WHICH IS INTENDED TO ASSIST THE RELEVANT MANAGEMENT OR TECHNICAL STAFF, WHETHER CLIENT OR SUPPLIER, IN PRODUCING A PROJECT-SPECIFIC TECHNICAL DESIGN DOCUMENT DOCUMENT. IT IS ALSO USEFUL BACKGROUND READING FOR ANYONE INVOLVED IN DEVELOPING OR MONITORING...
Words: 6668 - Pages: 27
...to keep up with changing technology. He would like to have a system that integrates all of the existing HR tools the company uses into a single, modern information systems application. This project will need to consist of several different stages in order for it to potentially be successful and will require an analyst to ensure all key points of the project are met. One of the first areas we need to look at when transitioning from analysis to design is the application software. “Software application architecture is the process of defining a structured solution that meets all of the technical and operational requirements, while optimizing common quality attributes such as performance, security, and manageability.” (Microsoft, 2014) Taking into account the requirements of the new design, a thin client-server architecture, where the server performs the application logic, makes the most sense to use. One of biggest benefits to a thin client-server architecture is that it is low cost and easy to maintain. Another great benefit to a thin client-server is that it is portable, which the company would greatly benefit from. Also, the client-server architecture supports a variety of clients and servers, making it more compatible with different brands of operating systems. Finally, this architecture can be adjusted to accommodate...
Words: 859 - Pages: 4
...Paper published in IEEE Software 12 (6) November 1995, pp. 42-50 Architectural Blueprints—The “4+1” View Model of Software Architecture Philippe Kruchten Rational Software Corp. Abstract This article presents a model for describing the architecture of software-intensive systems, based on the use of multiple, concurrent views. This use of multiple views allows to address separately the concerns of the various ‘stakeholders’ of the architecture: end-user, developers, systems engineers, project managers, etc., and to handle separately the functional and non functional requirements. Each of the five views is described, together with a notation to capture it. The views are designed using an architecture-centered, scenariodriven, iterative development process. Keywords: software architecture, view, object-oriented design, software development process Introduction We all have seen many books and articles where one diagram attempts to capture the gist of the architecture of a system. But looking carefully at the set of boxes and arrows shown on these diagrams, it becomes clear that their authors have struggled hard to represent more on one blueprint than it can actually express. Are the boxes representing running programs? Or chunks of source code? Or physical computers? Or merely logical groupings of functionality? Are the arrows representing compilation dependencies? Or control flows? Or data flows? Usually it is a bit of everything. Does an architecture need a single architectural...
Words: 6001 - Pages: 25
...Chief Operating Officer knows what every department is using to accomplish their work and can give feedback on certain applications being used. The Executive Assistant is good to gather information from as well because they know more than others about what is happening around the manufacturing plant. A couple floor employees working in the Human Resources Department would be useful as well because they use the programs on a daily basis and could have feedback on the applications they currently use and what is being requested for the new application. Key Factors The key factors needed to consider when gathering the information are: purpose, length, weaknesses, strengths, risks, cost, and economic value. For any project there needs to be a purpose for starting a project. The purpose needs to be precise and feasible. If the...
Words: 2189 - Pages: 9
...Software reusability TERM PAPER Software reusability is generally considered a way to solve the software development crisis. When we solve a problem we try to apply the solution to similar problems because that makes our work easy and simple. Now in this paper I would like to cover important aspects of software reusability. But one thing is for sure software reusability can improve software productivity. Software reuse has become a topic of much interest in the software community due to its potential benefits, which include increased product quality and decreased product cost and schedule. The most substantial benefits derive from a product line approach, where a common set of reusable software assets act as a base for subsequent similar products in a given functional domain. The upfront investments required for software reuse are considerable, and need to be duly considered prior to attempting a software reuse initiative. 1. Introduction Software reuse is the process of implementing or updating software systems using existing software components. A good software reuse process facilitates the increase of productivity, quality, and reliability, and the decrease of costs and implementation time. An initial investment is required to start a software reuse process, but that investment pays for itself in a few reuses. In short, the development of a reuse process and repository produces a base of knowledge that improves in quality after every reuse, minimizing the amount...
Words: 3225 - Pages: 13
...Successful Product Line Development and Sustainment: A DoD Case Study Sholom Cohen, Software Engineering Institute Ed Dunn, Naval Undersea Warfare Center Albert Soule, Software Engineering Institute September 2002 Product Line Systems Unlimited distribution subject to the copyright. Technical Note. CMU/SEI-2002-TN-018. The Software Engineering Institute is a federally funded research and development center sponsored by the U.S. Department of Defense. Copyright 2002 by Carnegie Mellon University. NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder. Internal use. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. External use. Requests for permission to reproduce this document or prepare derivative works of this document for external...
Words: 16988 - Pages: 68
...to follow the system development life cycle (SDLS) for it to be successful and have transformational effect on the company’s operation (Klein, S. 2007). If there is redundancy in the site of the company, some measures should be carried out to ensure that it functions well to serve the company’s information needs. There should be a back-up site available as a failover in case the main site goes down. There is also a need for the site to be redesigned to allow customers to order products online. The system development life cycle (SDLS) is involves seven phases or steps that are followed in developing an information system from conception up to disposition. The following is the seven-step phase of developing an information system by a software engineer: 1. Conceptual Planning 2. Planning and Requirements Definition 3. System design 4. Development and Testing 5. Implementation phase 6. Operations and Maintenance phase 7. Operations and Maintenance phase Conceptual Planning This is the first phase in the system development life cycle. In this phase the information system conceptual framework is constructed. This will include the evaluation and assessment of the system to be developed to determine the cost and risks associated with the system. The managers will also assess the benefits and the opportunities that will be associated with the system. In this first stage of the system development cycle, there will be also the division and designation of roles to be carried...
Words: 3420 - Pages: 14
...Olympic Competition in Physics in 2003 * Monash University International Scholarship for Excellence Student from 2005 till 2007. * The best Vietnamese technology student in 2005, 2006 * Monash Vice Chancellor’s Honours – PhD Scholarahip * Member of Australia Golden Key Society The combination between strong logic and critical thinking trained in Vietnam, with the practicality of computer technology trained in Australia has created his strong passion in creating novel optimal software solutions. He has more than 8 years extensive experience working as software solution provider in Australia. He has provided creative solutions for different challenging problems ranging from business, science and medical domain. At the moment, Dang is appointed as Business Intelligent Manager, leading the software development team in Clinical Integrated Solution, a group of different specialist clinics operating across Australia. He is the principal consultant and lead software architecture at I3 Solution. He is also doing his PhD in Medical Image Analysis at University of Western Australia. Our specialities: I3 Solution specialises in engineering high quality and...
Words: 3796 - Pages: 16
...Booch’s article “The Irrelevance of Architecture” (May/June 2007). Way too many people already feel that architecture is irrelevant, and they’ll be tempted to read the misleading title, skip the article, and forever use Booch as proof of their erroneous beliefs about architecture. Additionally, I should admonish Booch for the invalid assumptions and errors of omission his article propounded on the way to reaching an otherwise good conclusion—namely, that architecture is quite relevant. A better conclusion would have been that a proper systems architecture is vital, desires of the agile cowboy coding hackers notwithstanding. One always has an architecture. It might have been done explicitly; otherwise, it’s ultimately defined by whatever the developers came up with. It all depends on which end of the dog is wagging the other. And this is not some Big-Endian vs. Little-Endian religious dispute (see Danny Cohen’s article “On Holy Wars and a Plea for Peace” in the October 1981 issue of Computer). When it comes to dogs, the tail should be the thing wagged, just as a design should be dictated by an architecture. And architecture is relevant to the end users. Without starting with a proper systems architecture, the end result won’t serve users well. They might not care about the implementation details, but they do care that the interface and functionality suit their needs when delivered. Although Booch observes the generic relationship between architecture and implementation, he omits the...
Words: 1514 - Pages: 7
...System Architecture When we think about System Architecture and what does it really consist of; one may ask themselves what is it really and what are the components of it. System architecture is a system used to describe the overall design and structure of a computer network or system. System architecture translates the logical design of an information system into a physical structure that includes hardware, software, network support, processing methods and security. As information technology has expanded to include a wide range of physical devices, a method is required to organize and connect these items together in an organized manner. The term is also used to describe multifaceted computer software tools that include multiple modules. (Shelly & Rosenblatt, 2012) There are four main components to any system architecture; which are processing power, storage, connectivity, and user experience. The complexity of the system varies widely and is dependent upon user needs, business requirements, funding, and resource accessibility. It is imperative to note that system architecture must be malleable and able to meet changing needs quickly. A structure that is too rigid will not be able to accommodate new software or hardware. When it comes to building a payroll program I think the best architecture to use would be the client/server architecture. Client/server system generally refers to system that divide processing between one or more networked clients and a central server. We...
Words: 1065 - Pages: 5
...are few points that need to be considered before making the final decision. The goal of this report is to provide information and a guide to the process of creating a secure e-commerce site with minimum downtime. Considerations: There are a few factors that need to be considered before making the move to migrate the website. * Cost-Hardware, labor, software, etc. * Security-physical and physical * Physical space- structure, square footage, additional offices etc. Solution Using the System Development Life cycle we can define an efficient way to meet our set requirements and improve the existing website. Improving on the old foundation we can minimize costs, reduce project time and save the labor costs of having to start from scratch. This way we can focus on only redesigning parts we can’t recycle and improve on what we need to. Goals of the SDLC: * Deliver quality systems that meet or exceed customer expectations when promised and within cost estimates. * Provide a framework for developing quality systems using an identifiable, measurable, and repeatable process. * Establish a project management structure to ensure that...
Words: 1721 - Pages: 7
...reusable design fragment used to solve a commonly occurring problem in software development. Whereas, antipatterns are common design pitfalls that provide poor solutions to recurring design problems. Developers may unwillingly introduce anti-patterns in their software systems due to time pressure, lack of skills, communication or understanding. Anti-patterns have a negative effect on the comprehension and maintainability of a software system, and thus, understanding and detecting Anti-patterns provides the knowledge to prevent or recover from them. This paper discusses the anti-patterns of object oriented design, their symptoms, and consequences and issues related to their detection. This study also discusses some of the tools and approaches that are currently being developed and used in the software industry to detect anti-pattern. Towards the end, this paper also highlights some of the problems that are still open, to drive future research direction in this field. 1. Introduction Now-a-days, most of the software projects deal with large number of components that make the software more complicated and hard for novice designers to design. A design pattern is one of the most simple and powerful techniques used to improve the software design. Unfortunately, due to a number of market/customers constraints, anti-patterns may get introduced into the software systems and deteriorate its software quality. Hence, anti-patterns need to be carefully detected and monitored...
Words: 4918 - Pages: 20
...21 principles of enterprise architecture for the financial sector Thiago Souza Mendes Guimarães (tmendesg@br.ibm.com ) IT Architect IBM China 20 November 2012 The article lists the most relevant architectural principles for an IT department to follow in the financial market, with details about each principle. These principles are essential for an IT department to take on a strategic role in the company and to indicate actual value generation in IT decisions within an environment where pressure and business decisions are critical. Structure of these principles This article was developed with the purpose of proposing certain principles that must drive an enterprise architecture initiative. The main motivation that led to the development of this list is the difficulty of implementing enterprise architecture in an environment as hostile as the financial market. There is great pressure on the technology segment, which is usually not perceived as strategic. An even greater challenge is showing that IT decisions can add value and differentials to businesses. This list was organized and developed based on the selection and adjustment of the most relevant principles established throughout my experience in the financial market. Despite being selected within the financial segment context, most of these principles apply to any type of industry after only a few minor adjustments. Definitions Principles are high-level definitions of fundamental values that guide...
Words: 5320 - Pages: 22
...Model Driven Development – Future or Failure of Software Development? Ruben Picek, Vjeran Strahonja University of Zagreb, Faculty of Organization and Informatics, Varaždin ruben.picek@foi.hr, vjeran.strahonja@foi.hr Abstract. This article discusses some issues of the software development paradigm called Model Driven Development (MDD). Its basic idea is to move software development to a higher level of abstraction by using models as primary artifacts, and to transform models into the source code, with the aid of tools. Currently, there are several approaches to the realization of MDD paradigm which should bring a lot of benefits. However there are still problems to be solved, which will be discussed here. The authors are also going to analyze developers pros and cons, and give their own opinion about today's open question: Will MDD become a failure in trying to deal with software crisis, like the idea of CASE tools in 80's or will it become the future of software development? Keywords. MDD, MDD approaches, Software Factories, Software Development 1. Model Driven Development Paradigm In the last few years, software development has been faced with many challenges. Requirements of new and/or existing systems are growing, systems are complex and it is hard to build them on time and on budget. As an answer to these challenges, a wide spectrum of new approaches occurred, varying from buzzwords to comprehensive methodologies. One of the most prominent paradigms is Model Driven Development...
Words: 5437 - Pages: 22
...standardized operating system. They will begin to implement the new system in six months, and it will be operational by next year's second quarter. Riordan's HRIS system will be updated by a developing team, who will come up with a project plan and tell management what resources they need. To understand the project goal, the problem's domain and stakeholders must be identified. Interviewing different users will pinpoint particular problems in the system and begin to develop a possible solution. “Requirement elicitation must focus on the creation of requirements, not design activities, in order to adequately address users’ concerns and not just developer needs” (Christel & Kang, p. 18, 1992). Sometimes it is an indefinite goal to gather a problem's requirements, and it is possible that design language makes the unclear specifications unverifiable. The following techniques will be used to find specific user requirements. * Workshops- that facilitating meetings with many stakeholders. * Surveys – collecting information from stakeholders anonymously. * Documentation review – using company data to find requirements. Data flow diagrams can help illustrate the system's information. * Prototyping – coming up with models of the project at different stages of development. * Observation – developing requirements by observing natural users. * Focus groups (JAD sessions) – collaborative interviews with a...
Words: 2195 - Pages: 9
