[Skip Navigation] [CSUSB] / [CNS] / [Comp Sci & Eng Dept] / [R J Botting] / [CS372 Course Materials] [Search ] cs372/glossary.html Fri Nov 7 08:56:54 PST 2008 [Text Version] [About] [News] [Schedule] [Syllabus] [Glossary] [Contact] [Search] [Grades]
Readings Analysis [1] [2] [3] [4] [5] Choices [1] [2] [3] Data [1] [2] [3] [4] Requirements [1] [2] [3]
[Review] Field Trips [1] [2] [3] Project Iterations [1] [2] [3] [4] [5]

Contents

    CS372 Glossary

      Introduction

       People who study, use, and learn the following terms and phases will do better in this class than those who don't.

      Words and Phrases
    1. Acceptance::="Tests specified by a user or stake holder and carried out by them", if these fail then the system needs work. [ c2.html#Acceptance ]
    2. adaptive_maintenance::="Make system work in changing circumstances". [ a2.html#adaptive_maintenance ]
    3. API::= "Application Programmer Interface", a long list of functions [ d3.html#API ]
    4. Architecture::= Programs, data bases, modules, functions, components. [ r2.html#Architecture ]
    5. ASCII::="American Standard Code for Information Interchange". [ d2.html#ASCII ]
    6. audit_trail::="Know where data came from and be sure you know where it went.... All the way from input to output and storage". [ d1.html#audit_trail ]
    7. BCD::="binary coded decimal". [ d2.html#BCD ]
    8. bit::="Binary digIT", [ d2.html#bit ]
    9. bottom_up_testing::="Starts with unit tests and moves up to larger components until the whole system is tested". [ c2.html#bottom_up_testing ]
    10. byte::=2 nibbles. [ d2.html#byte ]
    11. Calculating present value of a project::=following [ c2.html#Calculating present value of a project ]
    12. closedown::="How to terminate a project". [ c3.html#closedown ]
    13. CMM::= "Capability Maturity Model", a model of how capable an organization is, [ c2.html#CMM ]
    14. Context_DFD::DFD=Shows a system as a single process surrounded by external entities. [ a4.html#Context_DFD ]
    15. corrective_maintenance::="Correct errors and defects discovered in the system". [ a2.html#corrective_maintenance ]
    16. Cost_benefit_analysis::= Benefits and costs; value of money; Break_even; Return_on investment, [ c2.html#Cost_benefit_analysis ]
    17. CRAP::acronym="Contrast, Repetition, Alignment, Proximity", The key principles of web design. [ d1.html#CRAP ]
    18. CRUD::acronym=Create + Read + Update + Delete. [ a4.html#CRUD ]
    19. CSS::="Cascading style sheets", change the detailed properties of elements in a web page. [ d1.html#CSS ]
    20. DBA::=Data Base Administrator. The guru who maintains the structure of a data base. [ d3.html#DBA ]
    21. DBMS::=Data Base Management Systems. [ d3.html#DBMS ]
    22. decision::=accept | delay | reject | refocus | purchase | enduser | out-source | open-source | modify_and_resubmit. [ c2.html#decision ]
    23. DFD::="A diagram that shows how data moves through a system through processes and stores, from sources to sinks". [ a4.html#DFD ]
    24. DFDs::="Data Flow Diagrams". [ a4.html#DFDs ]
    25. digit::=0..9. [ d2.html#digit ]
    26. DRY::="Don't Repeat Yourself", in computer code (data and program) say everything [ d1.html#DRY ]
    27. ERD::="A diagram showing Entity and Relation Types". [ d3.html#ERD ]
    28. Evaluating_an_idea::=following [ c1.html#Evaluating_an_idea ]
    29. executing::="main phase in a project" [ c3.html#executing ]
    30. Expected::= (Best+4*Most_Probable+Worst)/6. [ c3.html#Expected ]
    31. Fish_eye_DFD::DFD=Shows a DFD inside a box representing a process in another DFD. [ a4.html#Fish_eye_DFD ]
    32. For Money C, Time t, Rate r, PV(C,t,r)::= C/(1+r)**t. [ c2.html#PV ]
    33. Forsters_law::="Only Connect". [ c1.html#Forsters_law ]
    34. Four_phases_for_a_project::=initiation; planning; executing; closedown. [ c3.html#Four_phases_for_a_project ]
    35. HCI::="Human Computer Interface". [ d1.html#HCI ]
    36. HCI::="Human Computer Interface". [ d1.html#HCI ]
    37. IE4_URL_encoding::= [ r1.html#IE4_URL_encoding ]
    38. initiation::procedure="First phase in any project". [ c3.html#initiation ]
    39. Integration_test::="a test to see if a collection of tested components work as expected". [ c2.html#Integration_test ]
    40. ISO9000::="A set of ISO standards aimed at the quality of work done by an Enterprise", [ c2.html#ISO9000 ]
    41. ISO::="International Standard Organization". [ c2.html#ISO ]
    42. iteration::=Analyze_a_bit; Design_a_bit & Test; Refactor; Implement. [ a2.html#iteration ]
    43. JAD::="Joint Application Development". [ c2.html#JAD ]
    44. JDBC::="Java Data Base Connectivity". [ d3.html#JDBC ]
    45. JIT::="Just In Time". [ d1.html#JIT ]
    46. KISS::="Keep It Simple, Stupid". [ d1.html#KISS ]
    47. Level_0_DFD::=DFD=Shows the main functions in a system as processes.... [ a4.html#Level_0_DFD ]
    48. Level_1_DFD::DFD=Takes a single process in a Level_0_DFD and shows the details inside it. [ a4.html#Level_1_DFD ]
    49. metadata::jargon="data about data", for example the format of a date. [ a5.html#metadata ]
    50. nibble::= 4 bits. [ d2.html#nibble ]
    51. normalize::procedure="Required process for designing a workable relational data base". [ d4.html#normalize ]
    52. NPV::= "Net Present Value". Sum of all the present values. [ c2.html#NPV ]
    53. OCR::= Optical Character Recognition. [ a3.html#OCR ]
    54. OID::="Object Identifier", an invisible internal attribute associated with each object. [ d4.html#OID ]
    55. OLAP::="Online Analytical Processing". [ c1.html#OLAP ]
    56. OLTP::="Online Transaction Processing". [ c1.html#OLTP ]
    57. perfective_maintenance::="Make system work better: faster, cheaper, cleaner,..." [ a2.html#perfective_maintenance ]
    58. periodic_maintenance::="Scheduled down time for preventive maintenance". [ a2.html#periodic_maintenance ]
    59. period::=".".
    60. planning::=following [ c3.html#planning ]
    61. preventive_maintenance::="Regular inspection and improvement of all parts". [ a2.html#preventive_maintenance ]
    62. Problem_solving::=A framework for solving problems. [ c1.html#Problem_solving ]
    63. PSP::= See http://www.sei.cmu.edu/publications/documents/05.reports/05sr003.html [ a2.html#PSP ]
    64. refinement::=the process of filling in details, for example: going from the vision for a new system to a set of use cases, or the process of going from a use case name to a set of scenarios for a given use case. Moving from a rough or fuzzy idea to a more precise or clearer specification.
    65. regression_testing::="Repeating all previous tests each time a change is made", means you must store tests. [ c2.html#regression_testing ]
    66. SCM::="Software Configuration Management", [ c3.html#SCM ]
    67. sample_SDLC_details::=following, [ a2.html#sample_SDLC_details ]
    68. SDLC::= Analyze, Design, Implement, Operate & Support & Backup & Maintain, Discard. [ a2.html#SDLC ]
    69. SDLC::="System Development Life Cycle", an ideal model of [ a2.html#SDLC ]
    70. Slack::= earliest - latest, time spare in a noncritical activity in a project. [ c3.html#Slack ]
    71. Specification::report, [ c1.html#Specification ]
    72. SQA::= "Software Quality Assurance", [ c2.html#SQA ]
    73. SQL::="Structured Query Language", [ d3.html#SQL ]
    74. SSN::data_element=(0..9)^9, unique identifier for USA residents. [ a5.html#SSN ]
    75. SSR::form="System Service Request". [ c3.html#SSR ]
    76. stake_holder::="person who has a stake in the success of the system". [ c1.html#stake_holder ]
    77. stake_holders::="people who have a stake in the success of the system". [ c1.html#stake_holders ]
    78. subsystem::="a system that is part of a larger system", also known as a part [ a2.html#subsystem ]
    79. supersystem::="A system that contains this as a subsystem". [ a2.html#supersystem ]
    80. system::="a collection of interconnected parts". [ a2.html#system ]
    81. systemantics::= See http://en.wikipedia.org/wiki/Systemantics. [ a2.html#systemantics ]
    82. System_testing::="Top level integration test", [ c2.html#System_testing ]
    83. system_theory::= See http://en.wikipedia.org/wiki/System_theory. [ a2.html#system_theory ]
    84. TCO::=Total Cost of Ownership. [ c1.html#TCO ]
    85. TDD::="Test Driven Development", write code that does the testing [ c2.html#TDD ]
    86. TEC::CoRT=Target; Expand; Contract, [ c1.html#TEC ]
    87. top_down_testing::="tests the whole first with parts replaced by stubs until they are completed, and so on down". [ c2.html#top_down_testing ]
    88. Unit_test::="a test that finds out if a component is working up to its specification." [ c2.html#Unit_test ]
    89. URL_encoding::= [ r1.html#URL_encoding ]
    90. vision::="a statement of what the enterprise will achieve if a project is carried out". [ c1.html#vision ]
    91. work_book::artifact=following [ c3.html#work_book ]

      Abbreviations

    92. CASE::="Computer Aided Software Engineering", lead to IDE.
    93. CPM::="Critical Path Method".
    94. DFD::="Data Flow Diagram".
    95. DFDs::="Data Flow Diagrams", plural of DFD.
    96. ERD::="Entity Relation Diagrams".
    97. IDE::="Integated Developemnt Environment".
    98. IT::="Information Technology".
    99. JAD::="Joint Application Development".
    100. Logical::Ambrose_Bierce="In accordance with the speaker's thinking"
    101. Physical::="In accordance with the speaker's technology"
    102. RAD::="Rapid Application Development".
    103. SDLC::="Systems Development Life Cycle".
    104. TBA::="To Be Announced".
    105. TBD::="To Be Done".
    106. UML::=Unified Modeling Language.

    . . . . . . . . . ( end of section CS372 Glossary) <<Contents | End>>

    Abbreviations

  1. TBA::="To Be Announced".
  2. TBD::="To Be Done".

    Also see [ glossary.html ] for more special abbreviations and phrases.

End