Bibliographic items October-November 2005

Garfinkel05

1. Simson Garfinkel
2. Microsoft's Secret Bug Squasher
3. Wired (Nov 10 2005) [ 0,2924,69375,00.html?tw=wn_tophead_3 ]
4. =REPORT MS MODEL CHECKING DEVICE DRIVERS TOOL SLAM
5. So called formal methods -- math & logic -- are used inside Microsoft!

Firesmith05

1. Donald G Firesmith
2. Quality Requirements Checklist
3. JOT V4n9(Nov-Dec 2005)pp31-38 [ column4 ]
4. =HOWTO QUALITIES MODEL V&V
5. Stresses the importance of specifying (1) the conditions when the requirement applies, (2) a measurement, and (3) the minimum threshold value.
6. Quality_Requirement::= Net{conditions, criteria: Quality_subfactor, threshold: Quality_metric }.

Ng05

1. Pan-Wei Ng
2. Effective business modeling with UML: describing business use cases and realizations
3. IBM/Rational/library, downloaded (Nov 2005) [ 905.htm ]
4. =DEMO MODELING BUSINESS PROCESSES UML profile USE CASE
5. Business modeling profile: business use case, actors, workers, and entities.
6. A business use case describes how an (outside) actor gets value from the business.
7. "the true value in business modeling lies in understanding how seemingly piecemeal work-flows relate to each other."
   
8. (dick) |- "Do DFDs do it better?"
9. Realizations model work processes, process automation, & information processes as interaction diagrams, class diagrams, and use case diagrams.
10. One must choose names for messages so that they describe the responsibility of the receiving object.
11. "the value of business use cases is to put use cases in context... how a group... deliver[s] business value."

Molokken-OstvoldMagne Jorgensen05

1. Kjetil Molokken-Ostvold & Magne Jorgensen
2. A Comparison of Software Project Overruns -- flexible versus sequential development Models
3. IEEE Trans Software Engineering V31n 9(Sep 2005)pp754-766
4. =POLL INTERVIEWS 18 COMPANIES COST TIME ESTIMATION vs PROCESS AGILE SEQUENTIAL EVOLUTION ITERATION NORWAY
5. Effort. Sequential projects had bimodal estimates either accurate or 100% low. Flexible projects had estimates distributed about accurate.

SjobergEtAl05

1. Dag I K Sjoberg & Jo E Hannay & Ove Hansen & Vigdis By Kampenes & Amela Karahasanovlc & Nils-Kristian Liborg & Anette C Rekdal
2. A survey of controlled Experiments in Software engineering
3. IEEE Trans Software Engineering V31n9(Sep 2005)pp733-753
4. =survey 107 Experiments 1993..2002 replication validity journals
5. Less than 2% of 5k articles report controlled experiments

WangBastaniYen05

1. Dongfeng Wang & Farokh B Bastani & I.-Ling Yen
2. Automated Aspect-Oriented Decomposition of Process-Control Systems for Ultra-High Dependability Assurance
3. IEEE Trans Software Engineering V31n9(Sep 2005)pp713-732
4. =IDEA MATHEMATICS MODAL LOGIC TLA ASPECTS COMPONENTS NONDETERMINISTIC FSM RHSM IDEAL BART

VitolinsKalnins05

1. Valdis Vitolins& Audris Kalnins
2. Semantics of UML 2.0 Activity Diagram for Business Modeling by Means of Virtual Machine
3. Proc. Ninth IEEE Int'l EDOC Enterprise Computing Conf, IEEE(19-23 September 2005)pp181-192 [ 0509089 ]
4. =THEORY SEMantiCS UML2 activity Petrie nonsequential ADVM Object-Oriented metamodel workflow

Mercurius05

1. Neil Mercurius
2. 'Scrubbing' data for D3M
3. THE Journal V33n3(Oct 2005)pp15-18
4. =HOWTO DATA QUALITY D3M
5. Clean data before entering it in a central data base!
6. D3M::jargon=data-driven decision-making.
7. Define & enforce formats & coding.

Wagner05

1. Paul Wagner
2. Teaching Data Modeling: Process & Patterns
3. ACM SIGCSE Bulletin V37n2(Sep 2005) & ITiCSE 2005 proc pp168-172
4. =TYPE Data Modeling Patterns pedagogy
5. Need to spend more time on data modelling!
6. Data_modeling_patterns::=following,
   • (Aggregation): has_a:Company(1)-(*)Division.
   • (Intersection): Employer(1)-(*)Capability(*)-(1)Skill
   • Set(1)-(*)Member(*)-(1)Element.
   • List(1)-(*)Member(*)-(1)Element.
   • (Differing_Aspects): Address(*)-(1)Student(1)-(*)Phone.
   • (Subtypes): be: Full_Time_Employee(0..1)-(1)Employee.
   • (General_Association): manages: Employee(*)-(*)Department.
   • (Reflexive): manages: Employee (1)-(*) Employee.
   • tree: Node (1)-(*) Node.
   • (Graph): from: Edge (*)-(1) Node, to: Edge (*)-(1) Node,

. . . . . . . . . ( end of section Bibliographic items October-November 2005) <<Contents | End>>