01.02.2013 Views

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure out what dependencies<br />

this code has and if it has any<br />

impact on Orion’s Orbits’ code.<br />

Figure out how to package<br />

the compiled version to<br />

include in Orion’s Orbits.<br />

Document the code.<br />

Run a coverage report to see<br />

how much code you need to fix.<br />

Get a line count <strong>of</strong> the code and<br />

estimate how long it will take to fix.<br />

Do a security audit on the code.<br />

Use a UML tool to reverse-engineer<br />

the code and create class diagrams.<br />

So what about all the magnets we didn’t use?<br />

They’re not necessarily bad ideas, but here’s<br />

why we didn’t put them on our short list.<br />

This is important, but we don’t know what changes<br />

we’re going to have to make to the code yet. We’re just<br />

not ready to focus on library versions.<br />

This is going to be important once this code is stable,<br />

but until we get things tested and working, it’s not<br />

much use worrying about how to package anything up<br />

beyond the library we already have.<br />

Another important one, and it almost got a vertical<br />

spot next to “File bugs...”. But since we’re not making<br />

changes to the code yet, and don’t even know what<br />

parts we’ll need, we decided to leave this one <strong>of</strong>f <strong>of</strong> our<br />

short list...although we might come back to it later.<br />

This one just can’t happen yet. We don’t have tests, we<br />

don’t know what code we actually need, and we know<br />

some <strong>of</strong> the code isn’t working. Test coverage at this<br />

point won’t tell us much <strong>of</strong> value.<br />

This is oh-so-tempting. It provides a solid metric to<br />

latch onto, which seems like a good thing. The problem<br />

with this is that we don’t know how much <strong>of</strong> the<br />

code we’ll need, and we have absolutely no idea how<br />

much is missing. What if there is a stubbed-out class<br />

where a whole section <strong>of</strong> the library is supposed to be?<br />

Concerns like this make a metric here useless.<br />

At some point this will be a great idea, but like some <strong>of</strong><br />

the other tasks, we don’t know what code we need yet,<br />

and we’re about to go changing things anyway, so let’s<br />

hold <strong>of</strong>f on this for now.<br />

Of all the tasks we didn’t choose to do, this is the<br />

most likely candidate to get added back in. But right<br />

now, we don’t know how much <strong>of</strong> the library we need.<br />

Let’s get a handle on what we have to use; then we’ll<br />

try and figure out how it’s supposed to work.<br />

Download at WoweBook.Com<br />

bugs<br />

you are here 4 391

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!