100% tevredenheidsgarantie Direct beschikbaar na je betaling Lees online óf als PDF Geen vaste maandelijkse kosten
logo-home
Eerder door jou gezocht
Eerder door jou gezocht
logo
Brunel - Computer Science - Software engineering (pass) $27.23
In winkelwagen
Snel navigeren naar
Voorbeeld
  2.  
  3. Brunel University (BU)
  4.  
  5. Computer Science
  6.  
  7. Software engineering (CS3003)

Essay

Brunel - Computer Science - Software engineering (pass)
 4 keer verkocht
  • Vak
  • Software engineering (CS3003)
  • Instelling
  • Brunel University (BU)

This is an assignment I had completed during my final year at Brunel University for software engineering while studying computer science. This assignment was marked as pass or fail only. I had passed this assignment. This assignment includes me stating which metrics I believe are most important to ...

[Meer zien]
Laatste update van het document: 4 jaar geleden

Voorbeeld 1 van de 14  pagina's

Document informatie

  • 21 mei 2020
  • 16 december 2020
  • 14
  • 2019/2020
  • Essay
  • Onbekend
  • Onbekend

Onderwerpen

  • computer science
  • computing
  • computer

Geschreven voor

  • Brunel University (BU)
  • Computer Science
  • Software engineering (CS3003)
Alle documenten voor dit vak (2)

Verkoper

avatar-seller
xeon

Ontvangen beoordelingen

Voorbeeld van de inhoud

1)
I think the most important feature of code is class size. If a class becomes too large, then the class will become
too difficult to manage and is likely to result in more comments in comparison to if the class was broken down
to subclasses. If the class size is huge, then it is likely that it contains many methods and long methods
compared to if the class was broken down to subclasses, since when having multiple classes there are likely to
be more methods but more manageable chunks of code. Overall, large classes itself leads to other code smells
which have a highly negative impact, and therefore it would be best to avoid classes from being too large.

One metric would be weighted methods per class (Sommerville, 2011) if the complexity of the class becomes
too complex then it would be a good indicator to break the class into subclasses to keep the classes easy to
understand. Likewise, if a class isn’t complex enough it could be an indication to make the class a bit more
complex, otherwise it may become confusing managing too many classes.

Another metric would be depth of inheritance tree which takes the number of discrete levels in the
inheritance tree where subclasses inherit attributes and methods from super classes (Sommerville, 2011), if
the inheritance tree is too deep then it would mean the design is more complex, which would mean the design
of the classes would need to be looked into and perhaps if class sizes are too small and that’s the reason for
having a huge inheritance tree it could be better to have bigger class sizes.

Another metric would be number of children (Sommerville, 2011) as it measures the number of subclasses in a
class, it may be better to break a class into subclasses to make it easier to understand, although having too
many subclasses may make maintainability a bit more complicated, which is why it’s good to have a right
number of children.

Another metric would be coupling between object classes (Sommerville, 2011) if coupling is too highly
dependent between classes which means it is more likely changing one of the classes with the impact the
other classes within the program. If a class is too dependent it could then become difficult to break the class
into smaller subclasses which could lead to a large class.

2)
I chose project “Java” (GitHub, 2019). This project has 33 commits, 1 contributor, 0 releases, and 1 contributor.
From the contributor’s graph, the project’s first commit was on November 22 nd 2015 and last commit was on
November 30th 2015 which means the project is likely completed as it hasn’t been updated in so long.
Furthermore, the duration of the project was only 8 days. The contributor wrote 39958 lines and removed 386
lines, which means the contributor wrote a total of 39572 lines. There are over 2,700 forks which is probably
because the original owner of the repository hasn’t updated the repository in years, and users which have an
interest in this project have forked their own updated version so other users with an interest can use their
updated version instead. The project also has over 5,000-star rating which is considerably high for this
respiratory.

Dit zijn jouw voordelen als je samenvattingen koopt bij Stuvia:

Bewezen kwaliteit door reviews

Bewezen kwaliteit door reviews

Studenten hebben al meer dan 850.000 samenvattingen beoordeeld. Zo weet jij zeker dat je de beste keuze maakt!

In een paar klikken geregeld

In een paar klikken geregeld

Geen gedoe — betaal gewoon eenmalig met iDeal, creditcard of je Stuvia-tegoed en je bent klaar. Geen abonnement nodig.

Direct to-the-point

Direct to-the-point

Studenten maken samenvattingen voor studenten. Dat betekent: actuele inhoud waar jij écht wat aan hebt. Geen overbodige details!

Veelgestelde vragen

Wat krijg ik als ik dit document koop?

Je krijgt een PDF, die direct beschikbaar is na je aankoop. Het gekochte document is altijd, overal en oneindig toegankelijk via je profiel.

Tevredenheidsgarantie: hoe werkt dat?

Onze tevredenheidsgarantie zorgt ervoor dat je altijd een studiedocument vindt dat goed bij je past. Je vult een formulier in en onze klantenservice regelt de rest.

Van wie koop ik deze samenvatting?

Stuvia is een marktplaats, je koop dit document dus niet van ons, maar van verkoper xeon. Stuvia faciliteert de betaling aan de verkoper.

Zit ik meteen vast aan een abonnement?

Nee, je koopt alleen deze samenvatting voor $27.23. Je zit daarna nergens aan vast.

Is Stuvia te vertrouwen?

4,6 sterren op Google & Trustpilot (+1000 reviews)

Afgelopen 30 dagen zijn er 64257 samenvattingen verkocht

Opgericht in 2010, al 15 jaar dé plek om samenvattingen te kopen

Begin nu gratis

Laatst bekeken door jou

Case uitwerking ·

(1)

Financial Accounting - Case Uitwerking - Cloudpost

Samenvatting ·

(2)

Samenvatting Logistiek Verbeteren 4 - Warehousing en Fysieke Distributie H8-14 17/18

Voordeelbundel ·

(0)

Extramuraal CNA, RCA & Onco - Alles voor kennistoets & praktijktoets

Voordeelbundel ·

(0)

Literatuur en Kunst van China

Samenvatting ·

(0)

Samenvatting HK zietebeelden

Samenvatting ·

(0)

All lectures - Consumer Behaviour 2021

Voordeelbundel ·

(0)

Bundel Digitale Communicatie

Overig ·

(3)

IT-145 Grazioso Project Class files

Tentamen (uitwerkingen) ·

(0)

How to Read Literature Like a Professor Chapters 1-26 with complete solution

$27.23  4x  verkocht
  • (0)
In winkelwagen
Toegevoegd