| 1. Identity statement | ||||
| Reference Type | Conference Paper (Conference Proceedings) | |||
| Site | mtc-m16b.sid.inpe.br | |||
| Holder Code | isadg {BR SPINPE} ibi 8JMKD3MGPCW/3DT298S | |||
| Repository | dpi.inpe.br/ce@80/2007/01.21.06.28 (restricted access) | |||
| Last Update | 2007:04.06.20.50.26 (UTC) administrator | |||
| Metadata Repository | dpi.inpe.br/ce@80/2007/01.21.06.28.30 | |||
| Metadata Last Update | 2018:06.05.03.33.46 (UTC) administrator | |||
| Citation Key | Sosnin:2007:QuMeCo | |||
| Title | Question-answer means for collaborative development of software intensive systems  | |||
| Format | Print; CD-ROM; On-line. | |||
| Year | 2007 | |||
| Access Date | 2024, Apr. 27 | |||
| Secondary Type | CI | |||
| Number of Files | 3 | |||
| Size | 1692 KiB | |||
| 2. Context | ||||
| Author | Sosnin, Peter | |||
| Affiliation | Head of Computer Department of Ulianovsk State Technicval University (Russia) | |||
| Author e-Mail Address | sosnin@ulstu.ru | |||
| Editor | Loureiro, Geilson Curran, Ricky | |||
| e-Mail Address | sosnin@ulstu.ru | |||
| Conference Name | ISPE International Conference on Concurrent Engineering, 14 (CE 2007). | |||
| Conference Location | São José dos Campos | |||
| Date | 2007, July 16-20 | |||
| Publisher | Instituto Nacional de Pesquisas Espaciais (INPE) | |||
| Publisher City | São José dos Campos | |||
| Pages | 147-154 | |||
| Book Title | Proceedings | |||
| Organization | Instituto Nacional de Pesquisas Espaciais (INPE) | |||
| History (UTC) | 2007-03-27 17:26:45 :: sosnin@ulstu.ru -> ce2007 :: 2007-03-29 12:42:15 :: ce2007 -> sosnin@ulstu.ru :: 2007-04-06 12:13:30 :: sosnin@ulstu.ru -> ce2007 :: 2007-04-12 21:44:15 :: ce2007 -> administrator :: 2007-05-18 15:21:00 :: administrator -> ce2007 :: 2007-05-21 19:34:37 :: ce2007 -> administrator :: 2007-12-04 15:45:59 :: administrator -> sosnin@ulstu.ru :: 2007-12-04 19:49:58 :: sosnin@ulstu.ru -> administrator :: 2018-06-05 03:33:46 :: administrator -> marciana :: 2007 | |||
| 3. Content and structure | ||||
| Is the master or a copy? | is the master | |||
| Content Stage | completed | |||
| Transferable | 1 | |||
| Keywords | question-answer collaborative development software intensive systems | |||
| Abstract | Introduction. There is a problem of successful designing of the automated systems (AS) intensively using the software. The degree of successfulness, expressed through number of the projects which have come to the end according to initial intensions and plans, is extremely low (about 30 %). Success of creation the AS in an essential measure depends on conceptual interaction (and reasoning) of the persons involved in conceptual activity of the development process. So, experience of artificial intelligence connected with modeling of reasoning can be used for successful developing of the AS. This report presents the special workflows «Interaction with experience» which is based on question-answer modeling (QA-modeling) of the reasoning used in developing process. Such type of modeling is a useful source of positive effects for the AS. Question-answer reasoning. Question-answer reasoning and their models can help stakeholders to create mutual conceptual frameworks and understanding for developing of the AS. Construction of QA-model is considered completed if the set of conceptual models {MCk}, chosen for sufficient understanding of task Zi, is created. Thus, the conceptual decision of task Zi includes decisions of set of task {ZCk}, each of which is aimed at construction of corresponding model from set {MCk}. QA-models are the systematized representation of the reasoning, used during the decision of task Z(t) any type and kept in special QA-database. Any QA-model is a set of interactive objects such as question, answer and task with the certain attributes and operations. Essence of QA-modeling. The essence of QA-modeling defines interaction of stakeholders helped them: to enrich model QA(Z(t)); to realize a number of variants of the analysis (interactive (+ collective) inspection or validation of state QA (Z (t)) or its fragments, directed on revealing of mistakes and defects of design decisions, and also their conformity to norms and samples; the predicative analysis aimed at an establishment of adequacy of model); to use results of the analysis (for establishing of understanding and mutual understanding in group of the stakeholders; extracting of requirements and restrictions to the AS; managing of changes in the project; monitoring a state of designing process; achieving of other positive effects of development and its result. QA-processor. First of all QA-processor is a system for supporting of the collaborative design process. Its client-server architecture gives the members of a design team an opportunity to record QA-reasoning to the QA-database during the step-by-step designing. Designers interact operatively with objects of databases when interaction can give them the marked positive effects. The main application of the client is the Users workplace that provides an interface to work with QA-shell. All data and tools are on the server. When accessing the server functions from the users workplace user get an access to the client library. All components of processor are done through MIDAS-technology of Borland. QA-technology. It coordinates with Rational Unified Process and uses the tasks tree with iterative structure. This tree, any its fragment and any its task are opened in collaborative development environment for QA-modeling in any state and/or in any time. | |||
| Area | ETES | |||
| Type | Software Engineering and Simulation | |||
| doc Directory Content | access | |||
| source Directory Content |
| |||
| agreement Directory Content | there are no files | |||
| 4. Conditions of access and use | ||||
| Language | en | |||
| Target File | paper.pdf | |||
| User Group | administrator sosnin@ulstu.ru administrator | |||
| Visibility | shown | |||
| Read Permission | deny from all and allow from 150.163 | |||
| 5. Allied materials | ||||
| Host Collection | lcp.inpe.br/ignes/2004/02.12.18.39 cptec.inpe.br/walmeida/2003/04.25.17.12 | |||
| 6. Notes | ||||
| Mark | 1 | |||
| Empty Fields | archivingpolicy archivist callnumber contenttype copyholder copyright creatorhistory descriptionlevel dissemination documentstage doi edition group identifier isbn issn label lineage mirrorrepository nextedition nexthigherunit notes numberofvolumes orcid parameterlist parentrepositories previousedition previouslowerunit progress project readergroup resumeid rightsholder schedulinginformation secondarydate secondarykey secondarymark serieseditor shorttitle sponsor tertiarymark tertiarytype url versiontype volume | |||
| 7. Description control | ||||
| e-Mail (login) | marciana | |||
| update | ||||