Telmaco
-
P01 @ is specialist in software measurement, and measure/estimation of projects. Interested ITs welcome
11:29 AM May 27th
via TweetDeck
-
A01 - Tweetoriel A – Title: « How to measure software?
11:29 AM May 27th
via TweetDeck
-
P02: This Tweetoriel is the first of a series dedicated to software measurement and project estimation. COSMIC-talk Sequence
11:29 AM May 27th
via TweetDeck
-
P03: S1: How to measure software?, S2: Measuring software with COSMIC, S3: projects measurement, S4: Project benchmarking
11:28 AM May 27th
via TweetDeck
-
cosmictalk P03: S1: How to measure software?, S2: Measuring software with COSMIC, S3: projects measurement, S4: Project benchmarking
11:28 AM May 27th
via TweetDeck
-
P04: S5: Project estimation, S6: COSMIC and Agile, S7: Introduction to MeterIT-Cosmic
11:27 AM May 27th
via TweetDeck
-
P05: 25 Tweets are to appear. Your Tweets are welcome any time. Repeat the hashtag and code Axx in your Tweets
11:27 AM May 27th
via TweetDeck
-
A02 – Software offers a service to its users. --> functionality. Comparing components? Quantity of functionality?
11:27 AM May 27th
via TweetDeck
-
A03 – Since the advent of software, in the 60s, a number of methods have been in use: SLOC, IFPUG, MkII FPA, COSMIC
11:27 AM May 27th
via TweetDeck
-
A04 – SLOC (Source Lines Of Code) measures a number of source statements. Very poor approx. of the quantity of functionality
11:27 AM May 27th
via TweetDeck
-
A05 – SLOC appears late in the project – Too late for estimating the project. SLOC size depends on the coding language. Variable
11:26 AM May 27th
via TweetDeck
-
A06 – SLOC not rejected by CMMi, SPICE & others -> excess of trust. May be useful for dimensioning the object code memories
11:26 AM May 27th
via TweetDeck
-
A07 – SLOC is insufficient- Choose a better method. 3 measurement methods are currently available: MkII FPA, IFPUG, & COSMIC
11:26 AM May 27th
via TweetDeck
-
A08– IFPUG (IEEE TSE 1983). Identifies 5 artefacts: EI, EQ, EO, ILF & EIF. Counting rules exist, but based on conventions
11:25 AM May 27th
via TweetDeck
-
A09 – IFPUG appeared the first, hence, widely used. Can be used early in the project life cycle. Useful for estimation
11:25 AM May 27th
via TweetDeck
-
A10 – IFPUG may be inaccurate because of its conventions and inadequacy of its rules. It’s an evaluation by convention
11:25 AM May 27th
via TweetDeck
-
A12 – MkII FPA (1991) A piece of software holds a group of functional processes. Each is structured in a number of Transactions
11:20 AM May 27th
via TweetDeck
-
A13 – MkII FPA model: Transactions ‘description by <Entrees, Processes, Exits>.Entries and Exits depend on the N# of attributes
11:20 AM May 27th
via TweetDeck
-
A14 – Processes depends on the number of Entities referenced by Transactions. See method on
11:19 AM May 27th
via TweetDeck
-
A15 – MkII FPA is usable early in the PLC: useful for estimation. Not adequate for real-time apps. Is also based on conventions
11:19 AM May 27th
via TweetDeck
|
- Name B Londeix of Telmaco
- Location London
- Web http://www.telmac...
- Bio Telmaco Ltd's purpose is to make the MeterIT tool suite useful to software estimators. Software measurement, estimation, benchmark . . .
|