Information Technology (IT) Resources and Links
Tools
Software Estimation - NASA - Estimating the cost, schedule, and effort associated with a proposed software development project is a critical and challenging task. The software development industry, as a whole, does not have a good track record when it comes to completing a project on time and within budget. Recent studies have shown that only 25% of software development projects are completed successfully within the estimated schedule and budget. NASA is no exception to this problem.
Software Size Estimation - Industry as a whole must implement a more rigorous approach to estimating size. A proper size estimate can allow project planners to allocate appropriate amounts of time, money and people to the project. This, in turn, will assure that programmers have an appropriate amount of time for developing quality code and will also aid in providing accurate cost estimates for the customer. This paper will discuss some techniques and methods used in industry today to estimate size and provide some comments as to their benefits and drawbacks.
Guide to the Software Engineering Body of Knowledge - The software engineering body of knowledge is an all-inclusive term that describes the sum of knowledge within the profession of software engineering. Since it is usually not possible to put the full body of knowledge of even an emerging discipline, such as software engineering, into a single document, there is a need for a Guide to the Software Engineering Body of Knowledge. This Guide will seek to identify and describe that subset of the body of knowledge that is generally accepted, even though software engineers must be knowledgeable not only in software engineering, but also, of course, in other related disciplines. This has a downloadable version of the SWEBOK.
Basic COCOMO - This is a simple on-line cost model for estimating the number of person-months required to develop software. The model also estimates the development schedule in months and produces an effort and schedule distribution by major phases. This model is based on Barry Boehm's Constructive Cost Model (COCOMO). This is the top-level model, Basic COCOMO, which is applicable to the large majority of software projects.
Government
Federal IT Project Manager “(OPM Guidelines) – This interpretive guidance addresses position classification, job evaluation, staffing, qualifications, training, and development for project manager positions based on existing criteria and guidance.
Clinger-Cohen Act - Clinger-Cohen Act (CCA) of 1996 provides that the government information technology shop be operated exactly as an efficient and profitable business would be operated. Acquisition, planning and management of technology must be treated as a "capital investment." While the law is complex, all consumers of hardware and software in the Department should be aware of the Chief Information Officer's leadership in implementing this statute.
Government Performance and Results Act - The 1993 Government Performance and Results Act (GPRA), hold federal agencies accountable for using resources wisely and achieving program results. GPRA requires agencies to develop plans for what they intend to accomplish, measure how well they are doing, make appropriate decisions based on the information they have gathered, and communicate information about their performance to Congress and to the public. GPRA requires agencies to develop a five-year Strategic Plan, which includes a mission statement and sets out long-term goals and objectives; Annual Performance Plans, which provide annual performance commitments toward achieving the goals and objectives presented in the Strategic Plan; and Annual Performance Reports, which evaluate an agency's progress toward achieving performance commitments.
Software Technology Support Center (STSC) - In 1987, the U.S. Air Force selected Ogden Air Logistics Center (OO-ALC), Hill Air Force Base, Utah, to establish and operate its Software Technology Support Center (STSC). It was chartered to be the command focus for proactive application of software technology in weapon, command and control, intelligence and mission-critical systems.
Organizations
AIFP (Association of Information Technology Professionals) - AITP offers opportunities for Information Technology (IT) leadership and education through partnerships with industry, government and academia. AITP provides quality IT related education, information on relevant IT issues and forums for networking with experienced peers and other IT professionals for nearly 9,000 members. AITP is the Information Technology professional organization of choice for providing leadership opportunities, professional development and personal growth.
CMMI - (Software Engineering Institute)- Capability Maturity Model Integration ® (CMMI-SW®) describes the principles and practices underlying software process maturity and is intended to help software organizations improve the maturity of their software processes in terms of an evolutionary path from ad hoc, chaotic processes to mature, disciplined software processes.
ITIL - The Information Technology Infrastructure Library (ITIL) defines the organizational structure and skill requirements of an information technology organization and a set of standard operational management procedures and practices to allow the organization to manage an IT operation and associated infrastructure. The operational procedures and practices are supplier independent and apply to all aspects within the IT Infrastructure.
Manifesto for Agile Software Development – We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan