Submitted by Pedro Henrique Rodrigues (pedro.henriquer@ufpe.br) on 2015-03-04T17:46:47Z
No. of bitstreams: 2
dissertation_dmc4_final.pdf: 2547061 bytes, checksum: 37ab52f20fadfed5e6ba1cfb7649f971 (MD5)
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-04T17:46:47Z (GMT). No. of bitstreams: 2
dissertation_dmc4_final.pdf: 2547061 bytes, checksum: 37ab52f20fadfed5e6ba1cfb7649f971 (MD5)
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Previous issue date: 2012-02-16 / Since the very first graphical user interfaces, progress indicators have been widely used to provide
feedback regarding the execution of a system long-running tasks. In fact, practical experience
and formal experiments suggest that such indicators are an important user interface
tool, as they enhance the attractiveness and effectiveness of the programs that incorporate them.
However, in order to make progress feedback possible, the system services involved must provide
on-line monitoring capabilities. As the software systems become increasingly larger and
more complex — often involving complex interactions between various different components
and abstraction layers —, the crosscutting nature of monitoring concerns can introduce several
inherent challenges to the software development: (1) code quality degradation with respect
to tangling and scattering; (2) costly software evolution and maintenance difficulties; (3) absence
of specific development patterns and regular standardized process guidance; (4) loss of
development productivity; and (5) inconsistent monitoring results.
In this context, this work provides an analysis of monitoring requirements, possible approaches
towards its implementation along with an analysis of the main benefits and weaknesses
involved. Furthermore, it is proposed and evaluated a solution to aid the software development
by overcoming the monitoring-related inherent challenges, rather by mitigating or completely
eliminating the problems. The solution consists of a framework, extended libraries, and generic
software process guidelines regarding the monitoring requirements, with focus on the Rational
Unified Process (RUP), for exemplification purpose, but not limited to it.
| Identifer | oai:union.ndltd.org:IBICT/oai:repositorio.ufpe.br:123456789/10442 |
| Date | 16 February 2012 |
| Creators | CARDOSO, David Menezes |
| Contributors | SAMPAIO, Augusto Cesar Alves de |
| Publisher | Universidade Federal de Pernambuco |
| Source Sets | IBICT Brazilian ETDs |
| Language | English |
| Detected Language | English |
| Type | info:eu-repo/semantics/publishedVersion, info:eu-repo/semantics/masterThesis |
| Source | reponame:Repositório Institucional da UFPE, instname:Universidade Federal de Pernambuco, instacron:UFPE |
| Rights | Attribution-NonCommercial-NoDerivs 3.0 Brazil, http://creativecommons.org/licenses/by-nc-nd/3.0/br/, info:eu-repo/semantics/openAccess |
Page generated in 0.0019 seconds